From: Johannes Krottmayer <krjdev@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/3] drivers: spi: rk_spi: Add support for RK3328
Date: Wed, 8 Jul 2020 23:57:39 +0200 [thread overview]
Message-ID: <20200708215740.28515-3-krjdev@gmail.com> (raw)
In-Reply-To: <20200708215740.28515-1-krjdev@gmail.com>
Add support for the RK3328 SPI controller
Signed-off-by: Johannes Krottmayer <krjdev@gmail.com>
Cc: Kever Yang <kever.yang@rock-chips.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>
---
I don't know if "rk3399_spi_params" is also required for the
RK3328 SPI controller.
Probing, Reading, Writing and Erasing of a flash device works
with the SF command. Tested it with the PINE64 Rock64 board.
drivers/spi/rk_spi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/spi/rk_spi.c b/drivers/spi/rk_spi.c
index 833cb04922..0495e04945 100644
--- a/drivers/spi/rk_spi.c
+++ b/drivers/spi/rk_spi.c
@@ -545,7 +545,9 @@ const struct rockchip_spi_params rk3399_spi_params = {
};
static const struct udevice_id rockchip_spi_ids[] = {
+ { .compatible = "rockchip,rk3066-spi" },
{ .compatible = "rockchip,rk3288-spi" },
+ { .compatible = "rockchip,rk3328-spi" },
{ .compatible = "rockchip,rk3368-spi",
.data = (ulong)&rk3399_spi_params },
{ .compatible = "rockchip,rk3399-spi",
--
2.26.2
next prev parent reply other threads:[~2020-07-08 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 21:57 [PATCH 0/3] rockchip: rk3328: Add SPI support Johannes Krottmayer
2020-07-08 21:57 ` [PATCH 1/3] drivers: clk: rockchip: clk_rk3328: " Johannes Krottmayer
2020-07-18 3:06 ` Kever Yang
2020-07-08 21:57 ` Johannes Krottmayer [this message]
2020-07-18 3:06 ` [PATCH 2/3] drivers: spi: rk_spi: Add support for RK3328 Kever Yang
2020-07-08 21:57 ` [PATCH 3/3] ARM: dts: rk3328: Add SPI support Johannes Krottmayer
2020-07-18 3:06 ` Kever Yang
2020-07-18 14:28 ` [PATCH 0/3] rockchip: " Kever Yang
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=20200708215740.28515-3-krjdev@gmail.com \
--to=krjdev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.