From: Jagan Teki <jagan@amarulasolutions.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Pull request: u-boot-spi/next for next
Date: Wed, 30 Jun 2021 17:35:03 +0530 [thread overview]
Message-ID: <20210630120503.578697-1-jagan@amarulasolutions.com> (raw)
Hi Tom,
Please pull this PR for next.
Summary:
- Cypress s25hl-t/s25hs-t support (Takahiro Kuwano)
CI:
https://source.denx.de/u-boot/custodians/u-boot-spi/-/pipelines/7979
thanks,
Jagan.
The following changes since commit f6adec1af4b2f5d3012480c6cdce7743b74a6156:
mtd: spi-nor-core: Allow using Micron mt35xu512aba in Octal DTR mode (2021-06-28 12:06:57 +0530)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-spi next
for you to fetch changes up to 5b8ec59e2a219185127fcaa640c2f5d5aba3acd6:
mtd: spi-nor-tiny: Add fixups for Cypress s25hl-t/s25hs-t (2021-06-29 19:16:54 +0530)
----------------------------------------------------------------
Takahiro Kuwano (9):
mtd: spi-nor: Add Cypress manufacturer ID
mtd: spi-nor-ids: Add Cypress s25hl-t/s25hs-t
mtd: spi-nor-core: Add support for Read/Write Any Register
mtd: spi-nor-core: Add support for volatile QE bit
mtd: spi-nor-core: Add the ->ready() hook
mtd: spi-nor-core: Read status by Read Any Register
mtd: spi-nor-core: Add Cypress manufacturer ID in set_4byte
mtd: spi-nor-core: Add fixups for Cypress s25hl-t/s25hs-t
mtd: spi-nor-tiny: Add fixups for Cypress s25hl-t/s25hs-t
drivers/mtd/spi/spi-nor-core.c | 266 ++++++++++++++++++++++++++++++++++++++++-
drivers/mtd/spi/spi-nor-ids.c | 16 +++
drivers/mtd/spi/spi-nor-tiny.c | 6 +
include/linux/mtd/spi-nor.h | 11 ++
4 files changed, 297 insertions(+), 2 deletions(-)
next reply other threads:[~2021-06-30 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 12:05 Jagan Teki [this message]
2021-06-30 22:43 ` Pull request: u-boot-spi/next for next Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2021-06-28 15:51 Jagan Teki
2021-06-29 12:38 ` 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=20210630120503.578697-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