From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: vf610-zii-dev-rev-b: add hi8435 device
Date: Mon, 22 May 2017 09:20:18 -0700 [thread overview]
Message-ID: <a74ee28c1c62fee5a5e75dda70a02990@agner.ch> (raw)
In-Reply-To: <20170522131010.3537-1-nikita.yoush@cogentembedded.com>
On 2017-05-22 06:10, Nikita Yushchenko wrote:
> ZII dev board rev B has a Holt Hi8435 connected to dspi2.
> Add it to device tree.
>
> ZII dev board rev C does not have that, so use rev-b dts file,
> not common dtsi file.
>
> Signed-off-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
> ---
> arch/arm/boot/dts/vf610-zii-dev-rev-b.dts | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
> b/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
> index 37f95427616f..f433465c3a7c 100644
> --- a/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
> +++ b/arch/arm/boot/dts/vf610-zii-dev-rev-b.dts
> @@ -348,6 +348,25 @@
> };
> };
>
> +&edma1 {
> + status = "okay";
> +};
> +
> +&dspi2 {
> + bus-num = <1>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_dspi2>;
> + status = "okay";
> + spi-num-chipselects = <2>;
> +
> + hi8435 at 1 {
> + compatible = "holt,hi8435";
> + reg = <1>;
> + spi-max-frequency = <20000000>;
> + gpios = <&gpio5 3 0>;
Nit: GPIO_ACTIVE_HIGH instead of 0?
--
Stefan
> + };
> +};
> +
> &i2c0 {
> clock-frequency = <100000>;
> pinctrl-names = "default";
next prev parent reply other threads:[~2017-05-22 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 13:10 [PATCH] ARM: dts: vf610-zii-dev-rev-b: add hi8435 device Nikita Yushchenko
2017-05-22 16:20 ` Stefan Agner [this message]
2017-05-22 16:29 ` Nikita Yushchenko
2017-05-22 18:21 ` Andrew Lunn
2017-05-23 6:02 ` Nikita Yushchenko
2017-05-25 7:19 ` Shawn Guo
2017-05-25 8:03 ` Nikita Yushchenko
2017-05-28 15:09 ` Jonathan Cameron
2017-05-25 7:00 ` Shawn Guo
2017-05-25 8:06 ` Nikita Yushchenko
2017-05-25 8:20 ` Shawn Guo
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=a74ee28c1c62fee5a5e75dda70a02990@agner.ch \
--to=stefan@agner.ch \
--cc=linux-arm-kernel@lists.infradead.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).