From: Johan Jonker <jbx6244@gmail.com>
To: broonie@kernel.org
Cc: robh+dt@kernel.org, mark.rutland@arm.com, heiko@sntech.de,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/3] dt-bindings: spi: spi-rockchip: add description for rk3328
Date: Wed, 22 Jan 2020 23:45:55 +0100 [thread overview]
Message-ID: <20200122224555.6845-3-jbx6244@gmail.com> (raw)
In-Reply-To: <20200122224555.6845-1-jbx6244@gmail.com>
The description below is already in use for rk3328.dtsi,
but was somehow never added to a document, so add
"rockchip,rk3328-spi", "rockchip,rk3066-spi"
for spi nodes on a rk3328 platform to spi-rockchip.yaml.
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
Acked-by: Rob Herring <robh@kernel.org>
---
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 a797a4748..5e0fab1bc 100644
--- a/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
+++ b/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
@@ -30,6 +30,7 @@ properties:
- rockchip,rk3188-spi #for rk3188 SoCs.
- rockchip,rk3288-spi #for rk3288 SoCs.
- rockchip,rk3308-spi #for rk3308 SoCs.
+ - rockchip,rk3328-spi #for rk3328 SoCs.
- rockchip,rk3368-spi #for rk3368 SoCs.
- rockchip,rk3399-spi #for rk3399 SoCs.
- const: rockchip,rk3066-spi
--
2.11.0
prev parent reply other threads:[~2020-01-22 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 22:45 [PATCH v2 1/3] dt-bindings: spi: convert rockchip spi bindings to yaml Johan Jonker
[not found] ` <20200122224555.6845-1-jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-01-22 22:45 ` [PATCH v2 2/3] dt-bindings: spi: spi-rockchip: add description for rk3308 Johan Jonker
2020-03-04 17:10 ` [PATCH v2 1/3] dt-bindings: spi: convert rockchip spi bindings to yaml Mark Brown
2020-01-22 22:45 ` Johan Jonker [this message]
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=20200122224555.6845-3-jbx6244@gmail.com \
--to=jbx6244@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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 \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).