From: Benoit Cousson <bcousson@baylibre.com>
To: Eric Witcher <ewitcher@mindspring.com>,
nm@ti.com, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap5-uevm: fix mcspi node pin descriptions
Date: Tue, 22 Oct 2013 16:54:03 +0200 [thread overview]
Message-ID: <5266918B.8070109@baylibre.com> (raw)
In-Reply-To: <1382078554-31628-1-git-send-email-ewitcher@mindspring.com>
Hi Eric,
On 18/10/2013 08:42, Eric Witcher wrote:
> Correct mcspi pin descriptions to match corresponding node name and
> add chip select number to be consistent with OMAP5 TRM.
>
> Signed-off-by: Eric Witcher <ewitcher@mindspring.com>
Applied on my tree.
Thanks,
Benoit
> ---
> arch/arm/boot/dts/omap5-uevm.dts | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
> index d784b3a..90c7843 100644
> --- a/arch/arm/boot/dts/omap5-uevm.dts
> +++ b/arch/arm/boot/dts/omap5-uevm.dts
> @@ -131,25 +131,25 @@
> 0xbc (PIN_INPUT | MUX_MODE0) /* mcspi2_clk */
> 0xbe (PIN_INPUT | MUX_MODE0) /* mcspi2_simo */
> 0xc0 (PIN_INPUT_PULLUP | MUX_MODE0) /* mcspi2_somi */
> - 0xc2 (PIN_OUTPUT | MUX_MODE0) /* mcspi2_cs */
> + 0xc2 (PIN_OUTPUT | MUX_MODE0) /* mcspi2_cs0 */
> >;
> };
>
> mcspi3_pins: pinmux_mcspi3_pins {
> pinctrl-single,pins = <
> - 0x78 (PIN_INPUT | MUX_MODE1) /* mcspi2_somi */
> - 0x7a (PIN_INPUT | MUX_MODE1) /* mcspi2_cs */
> - 0x7c (PIN_INPUT | MUX_MODE1) /* mcspi2_simo */
> - 0x7e (PIN_INPUT | MUX_MODE1) /* mcspi2_clk */
> + 0x78 (PIN_INPUT | MUX_MODE1) /* mcspi3_somi */
> + 0x7a (PIN_INPUT | MUX_MODE1) /* mcspi3_cs0 */
> + 0x7c (PIN_INPUT | MUX_MODE1) /* mcspi3_simo */
> + 0x7e (PIN_INPUT | MUX_MODE1) /* mcspi3_clk */
> >;
> };
>
> mcspi4_pins: pinmux_mcspi4_pins {
> pinctrl-single,pins = <
> - 0x164 (PIN_INPUT | MUX_MODE1) /* mcspi2_clk */
> - 0x168 (PIN_INPUT | MUX_MODE1) /* mcspi2_simo */
> - 0x16a (PIN_INPUT | MUX_MODE1) /* mcspi2_somi */
> - 0x16c (PIN_INPUT | MUX_MODE1) /* mcspi2_cs */
> + 0x164 (PIN_INPUT | MUX_MODE1) /* mcspi4_clk */
> + 0x168 (PIN_INPUT | MUX_MODE1) /* mcspi4_simo */
> + 0x16a (PIN_INPUT | MUX_MODE1) /* mcspi4_somi */
> + 0x16c (PIN_INPUT | MUX_MODE1) /* mcspi4_cs0 */
> >;
> };
>
>
--
Benoît Cousson
BayLibre
Embedded Linux Technology Lab
www.baylibre.com
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-10-22 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 6:42 [PATCH] ARM: dts: omap5-uevm: fix mcspi node pin descriptions Eric Witcher
2013-10-22 14:54 ` Benoit Cousson [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=5266918B.8070109@baylibre.com \
--to=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ewitcher@mindspring.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
/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