From: Stefan Agner <stefan@agner.ch>
To: Cory Tusar <cory.tusar@pid1solutions.com>
Cc: shawnguo@kernel.org, kernel@pengutronix.de, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch, Chris.Healy@zii.aero, Keith.Vennel@zii.aero
Subject: Re: [PATCH] ARM: dts: vfxxx: Fix dspi[01] spi-num-chipselects.
Date: Wed, 18 Nov 2015 22:36:40 -0800 [thread overview]
Message-ID: <a2287b99e8f9aa378e9c7c3750d1a7e5@agner.ch> (raw)
In-Reply-To: <1447905280-5172-1-git-send-email-cory.tusar@pid1solutions.com>
On 2015-11-18 19:54, Cory Tusar wrote:
> Per the Vybrid Reference Manual (section 3.8.6.1), dspi0 has 6 chip
> select signals associated with it, while dspi1 has only 4.
That is right, verified by in my RM!
Acked-by: Stefan Agner <stefan@agner.ch>
>
> Signed-off-by: Cory Tusar <cory.tusar@pid1solutions.com>
> ---
> arch/arm/boot/dts/vfxxx.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
> index 6736bae..1cca43a 100644
> --- a/arch/arm/boot/dts/vfxxx.dtsi
> +++ b/arch/arm/boot/dts/vfxxx.dtsi
> @@ -158,7 +158,7 @@
> interrupts = <67 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&clks VF610_CLK_DSPI0>;
> clock-names = "dspi";
> - spi-num-chipselects = <5>;
> + spi-num-chipselects = <6>;
> status = "disabled";
> };
>
> @@ -170,7 +170,7 @@
> interrupts = <68 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&clks VF610_CLK_DSPI1>;
> clock-names = "dspi";
> - spi-num-chipselects = <5>;
> + spi-num-chipselects = <4>;
> status = "disabled";
> };
next prev parent reply other threads:[~2015-11-19 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 3:54 Cory Tusar
2015-11-19 6:36 ` Stefan Agner [this message]
2015-11-24 9:49 ` 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=a2287b99e8f9aa378e9c7c3750d1a7e5@agner.ch \
--to=stefan@agner.ch \
--cc=Chris.Healy@zii.aero \
--cc=Keith.Vennel@zii.aero \
--cc=andrew@lunn.ch \
--cc=cory.tusar@pid1solutions.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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
all inboxes | Powered by JetHome®