From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 0/5] riscv: sifive/fu540: Enable SPI-NOR support
Date: Thu, 23 Apr 2020 22:30:52 +0530 [thread overview]
Message-ID: <20200423170057.1976-1-jagan@amarulasolutions.com> (raw)
This is series v4 for SPI-NOR support on SiFive FU540
platform with HiFive Unleashed board.
Here is the previous version changes[1].
All patches on top of u-boot-spi/master.
Changes for v4:
- add spi-mem exec_op
- rebase on master
Changes for v3:
- fixed QPP support
- dropped sf commands log
[1] https://patchwork.ozlabs.org/project/uboot/cover/20200420125238.9610-1-jagan at amarulasolutions.com/
Any inputs?
Jagan.
Jagan Teki (5):
spi: sifive: Add spi-mem exec op
spi: sifive: Fix format register proto field
spi: sifive: Fix QPP transfer
riscv: dts: hifive-unleashed-a00: Add -u-boot.dtsi
sifive: fu540: Enable spi-nor flash support
.../dts/hifive-unleashed-a00-u-boot.dtsi | 11 ++
board/sifive/fu540/Kconfig | 3 +
drivers/spi/spi-sifive.c | 156 +++++++++++++++---
3 files changed, 146 insertions(+), 24 deletions(-)
create mode 100644 arch/riscv/dts/hifive-unleashed-a00-u-boot.dtsi
--
2.17.1
next reply other threads:[~2020-04-23 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 17:00 Jagan Teki [this message]
2020-04-23 17:00 ` [PATCH v4 1/5] spi: sifive: Add spi-mem exec op Jagan Teki
2020-04-23 17:00 ` [PATCH v4 2/5] spi: sifive: Fix format register proto field Jagan Teki
2020-04-23 17:00 ` [PATCH v4 3/5] spi: sifive: Fix QPP transfer Jagan Teki
2020-04-23 17:00 ` [PATCH v4 4/5] riscv: dts: hifive-unleashed-a00: Add -u-boot.dtsi Jagan Teki
[not found] ` <752D002CFF5D0F4FA35C0100F1D73F3FA46FCB06@ATCPCS16.andestech.com>
2020-04-27 1:55 ` Rick Chen
2020-04-23 17:00 ` [PATCH v4 5/5] sifive: fu540: Enable spi-nor flash support Jagan Teki
[not found] ` <752D002CFF5D0F4FA35C0100F1D73F3FA46FCB21@ATCPCS16.andestech.com>
2020-04-27 2:00 ` Rick Chen
2020-04-24 18:18 ` [PATCH v4 0/5] riscv: sifive/fu540: Enable SPI-NOR support Sagar Kadam
2020-04-25 11:08 ` Jagan Teki
[not found] ` <752D002CFF5D0F4FA35C0100F1D73F3FA46FC853@ATCPCS16.andestech.com>
2020-04-27 0:16 ` Rick Chen
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=20200423170057.1976-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