From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: Pull request: u-boot-spi/master
Date: Fri, 26 Feb 2021 22:52:12 +0530 [thread overview]
Message-ID: <20210226172212.104405-1-jagan@amarulasolutions.com> (raw)
Hi Tom,
Please pull this PR.
Summary:
- new GigaDevice flash ids
- fixes for imx, nxp_spi drivers
GitLab CI:
https://gitlab.denx.de/u-boot/custodians/u-boot-spi/-/pipelines/6528
The following changes since commit c28d5d704d3347fcbe5e49ab561973c00bf9337f:
Merge branch '2021-02-25-remove-platforms' (2021-02-25 13:18:27 -0500)
are available in the Git repository at:
https://gitlab.denx.de/u-boot/custodians/u-boot-spi master
for you to fetch changes up to 783a15b35131abc599ec6deca55cf841d2e7c208:
mtd: nand: spi: Support GigaDevice GD5F1GQ5UExxG (2021-02-26 16:01:37 +0530)
----------------------------------------------------------------
Adam Ford (1):
spi: nxp_fspi: Fix error reporting
Alper Nebi Yasak (1):
mtd: spi-nor-ids: Add Gigadevice GD25LQ64C
Bin Meng (1):
mtd: spi-nor.h: Change spaces to tabs
Hauke Mehrtens (1):
mtd: nand: spi: Only one dummy byte in QUADIO
Marek Vasut (1):
spi: imx: Implement set_speed
Reto Schneider (1):
mtd: nand: spi: Support GigaDevice GD5F1GQ5UExxG
Sean Anderson (3):
cmd: sf: Display errno on erase failure
cmd: sf: Print error on test failure
mtd: spi-nor-core: Fix typo in documentation
Su Baocheng (1):
mtd: spi-nor-ids: Add support of flash protection to w25q128
cmd/sf.c | 29 ++++++++------
drivers/mtd/nand/spi/gigadevice.c | 79 ++++++++++++++++++++++++++++++++++-----
drivers/mtd/spi/spi-nor-ids.c | 10 ++++-
drivers/spi/mxc_spi.c | 5 ++-
drivers/spi/nxp_fspi.c | 4 +-
include/linux/mtd/spi-nor.h | 22 +++++------
6 files changed, 113 insertions(+), 36 deletions(-)
next reply other threads:[~2021-02-26 17:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 17:22 Jagan Teki [this message]
2021-02-26 20:10 ` Pull request: u-boot-spi/master Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 14:33 Jagan Teki
2024-10-24 20:42 ` Tom Rini
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-07-18 19:35 Jagan Teki
2022-07-19 14:51 ` 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
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=20210226172212.104405-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.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