From: Jagan Teki <jagan@amarulasolutions.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Pull request: u-boot-spi/master
Date: Tue, 19 Jul 2022 01:05:15 +0530 [thread overview]
Message-ID: <20220718193515.5533-1-jagan@amarulasolutions.com> (raw)
Hi Tom,
Please pull this PR.
Summary:
- add Macronix Octal flash (JaimeLiao)
CI:
https://source.denx.de/u-boot/custodians/u-boot-spi/-/pipelines/12778
thanks,
Jagan.
The following changes since commit 26f6f7fb5c0651d65afdee6d8ed36063606179a8:
Merge branch '2022-07-14-migrate-wiki-to-sphinx' (2022-07-14 18:43:51 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-spi master
for you to fetch changes up to 47ed8b22fd561b65e8541919becc76ab3d86f7a3:
mtd: spi-nor-ids: add winbond w25q512nw family support (2022-07-18 19:15:19 +0530)
----------------------------------------------------------------
Jae Hyun Yoo (1):
mtd: spi-nor-ids: add winbond w25q512nw family support
JaimeLiao (4):
mtd: spi-nor: add support for Macronix Octal flash
mtd: spi-nor-core: Adding different type of command extension in Soft Reset
mtd: spi-nor: Parse SFDP SCCR Map
mtd: spi-nor-core: Add support for Macronix Octal flash
Jan Kiszka (2):
mtd: spi: Convert is_locked callback to is_unlocked
sf: Query write-protection status before operating the flash
Vaishnav Achath (1):
spl: spl_spi: add spi_nor_remove() to soft reset flash
cmd/sf.c | 12 +++
common/spl/spl_spi.c | 5 ++
drivers/mtd/spi/Kconfig | 7 ++
drivers/mtd/spi/spi-nor-core.c | 167 +++++++++++++++++++++++++++++++++++++----
drivers/mtd/spi/spi-nor-ids.c | 29 ++++++-
include/linux/mtd/spi-nor.h | 17 ++++-
6 files changed, 219 insertions(+), 18 deletions(-)
next reply other threads:[~2022-07-18 19:35 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 19:35 Jagan Teki [this message]
2022-07-19 14:51 ` Pull request: u-boot-spi/master Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2024-01-29 17:53 Jagan Teki
2024-01-29 18:50 ` Tom Rini
2023-07-13 16:36 Jagan Teki
2023-07-14 16:05 ` Tom Rini
2023-05-01 17:12 Jagan Teki
2023-05-01 22:46 ` Tom Rini
2023-01-26 17:52 Jagan Teki
2023-01-26 20:09 ` Tom Rini
2022-11-02 6:08 Jagan Teki
2022-11-02 15:34 ` Tom Rini
2022-10-25 12:26 Jagan Teki
2022-10-25 16:27 ` Tom Rini
2022-05-04 6:11 Jagan Teki
2022-05-04 15:41 ` Tom Rini
2022-03-12 8:44 Jagan Teki
2022-03-13 12:17 ` Tom Rini
2021-12-26 18:57 Jagan Teki
2021-12-27 13:25 ` Tom Rini
2021-10-23 13:35 Jagan Teki
2021-10-23 20:10 ` Tom Rini
2021-08-03 16:24 Jagan Teki
2021-08-04 1:14 ` Tom Rini
2021-02-26 17:22 Jagan Teki
2021-02-26 20:10 ` Tom Rini
2020-12-18 17:54 Jagan Teki
2020-12-20 23:06 ` Tom Rini
2020-07-20 17:14 Jagan Teki
2020-07-22 3:04 ` Tom Rini
2020-07-11 17:02 Jagan Teki
2020-07-13 15:28 ` Tom Rini
2020-06-11 17:53 Jagan Teki
2020-06-14 16:00 ` Tom Rini
2020-06-02 18:54 Jagan Teki
2020-06-03 18:09 ` Tom Rini
2020-05-09 16:26 Jagan Teki
2020-05-09 20:58 ` Tom Rini
2020-05-10 14:19 ` Jagan Teki
2020-05-10 19:36 ` Tom Rini
2020-04-21 8:24 Jagan Teki
2020-04-21 19:19 ` Tom Rini
2020-04-03 14:30 Jagan Teki
2020-04-05 23:04 ` Tom Rini
2020-01-27 17:48 Jagan Teki
2020-01-28 16:04 ` Tom Rini
2019-12-27 12:20 Jagan Teki
2019-12-28 4:30 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220718193515.5533-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).