From: Jon Lin <jon.lin@rock-chips.com>
To: broonie@kernel.org
Cc: heiko@sntech.de, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel@esmil.dk, Jon Lin <jon.lin@rock-chips.com>
Subject: [PATCH v2 3/8] dt-bindings: spi: spi-rockchip: add description for rv1126
Date: Tue, 27 Apr 2021 15:37:28 +0800 [thread overview]
Message-ID: <20210427073733.31419-3-jon.lin@rock-chips.com> (raw)
In-Reply-To: <20210427073733.31419-1-jon.lin@rock-chips.com>
The description below will be used for rv1126.dtsi in the future
Signed-off-by: Jon Lin <jon.lin@rock-chips.com>
---
Documentation/devicetree/bindings/spi/spi-rockchip.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-rockchip.yaml b/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
index 1e6cf29e6388..4ed5b72a8494 100644
--- a/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
+++ b/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
@@ -27,6 +27,7 @@ properties:
- items:
- enum:
- rockchip,px30-spi
+ - rockchip,rv1126-spi
- rockchip,rk3188-spi
- rockchip,rk3288-spi
- rockchip,rk3308-spi
--
2.17.1
next prev parent reply other threads:[~2021-04-27 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 7:37 [PATCH v2 1/8] spi: rockchip: Set rx_fifo interrupt waterline base on transfer item Jon Lin
2021-04-27 7:37 ` [PATCH v2 2/8] spi: rockchip: Wait for STB status in slave mode tx_xfer Jon Lin
2021-05-05 7:59 ` Sascha Hauer
2021-04-27 7:37 ` Jon Lin [this message]
2021-04-27 7:37 ` [PATCH v2 4/8] spi: rockchip: add compatible string for rv1126 Jon Lin
2021-04-27 7:37 ` [PATCH v2 5/8] spi: rockchip: Support cs-gpio Jon Lin
2021-04-27 7:38 ` [PATCH v2 6/8] dt-bindings: spi: spi-rockchip: add description for rk3568 Jon Lin
2021-04-27 7:38 ` [PATCH v2 7/8] spi: rockchip: Add compatible string " Jon Lin
2021-04-27 7:38 ` [PATCH v2 8/8] spi: rockchip: Support SPI_CS_HIGH Jon Lin
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=20210427073733.31419-3-jon.lin@rock-chips.com \
--to=jon.lin@rock-chips.com \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@esmil.dk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
/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).