u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
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: Wed,  4 May 2022 11:41:08 +0530	[thread overview]
Message-ID: <20220504061108.4949-1-jagan@amarulasolutions.com> (raw)

Hi Tom,

Please pull this PR.

Summary:
- NPCM7xx FIU SPI driver (Jim Liu)
- AT45DB641E dataflash (Luca Ellero) 

CI:
https://source.denx.de/u-boot/custodians/u-boot-spi/-/pipelines/11912

thanks,
Jagan.

The following changes since commit c70c0102af5413cadde6bf90044cb75aefef0584:

  Merge tag 'efi-2022-07-rc2' of https://source.denx.de/u-boot/custodians/u-boot-efi (2022-04-29 14:04:08 -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 c62f93a620f7c13564a0f4a5583e90a01047901d:

  sf: dataflash: add support for AT45DB641E (2022-05-03 17:57:19 +0530)

----------------------------------------------------------------
Jim Liu (1):
      spi: npcm-fiu: add NPCM7xx FIU controller driver

Luca Ellero (2):
      sf: dataflash: add support for "extended ID"
      sf: dataflash: add support for AT45DB641E

Marek Vasut (1):
      mtd: spi-nor-ids: Add Winbond W25Q128JW ID

Tien Fong Chee (1):
      mtd: spi-nor-ids: add Macronix mx25u51245g flash entry

 drivers/mtd/spi/sf_dataflash.c | 101 +++++++----
 drivers/mtd/spi/spi-nor-ids.c  |   7 +
 drivers/spi/Kconfig            |   6 +
 drivers/spi/Makefile           |   1 +
 drivers/spi/npcm_fiu_spi.c     | 387 +++++++++++++++++++++++++++++++++++++++++
 5 files changed, 468 insertions(+), 34 deletions(-)
 create mode 100644 drivers/spi/npcm_fiu_spi.c

             reply	other threads:[~2022-05-04  6:11 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  6:11 Jagan Teki [this message]
2022-05-04 15:41 ` 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-07-18 19:35 Jagan Teki
2022-07-19 14:51 ` 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=20220504061108.4949-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).