From: Benoit Cousson <b-cousson@ti.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: tony@atomide.com, grant.likely@secretlab.ca, eballetbo@gmail.com,
elezegarcia@gmail.com, ebutera@gmail.com,
javier.martinez@collabora.co.uk, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm: dts: Add uart1 and uart2 to igep boards.
Date: Wed, 12 Dec 2012 17:09:32 +0100 [thread overview]
Message-ID: <50C8AC3C.9020908@ti.com> (raw)
In-Reply-To: <1355326422-12357-1-git-send-email-matthias.bgg@gmail.com>
Hi Matthias,
On 12/12/2012 04:33 PM, Matthias Brugger wrote:
> This patch is a follow-up patch for Javier Martinez effort adding initial
> device tree support to IGEP technology devices. [1]
>
> It adds uart1 and uart2 bindings to the generic dtsi for the IGEP boards.
>
> [1] http://www.spinics.net/lists/linux-omap/msg83409.html
>
> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> arch/arm/boot/dts/omap3-igep.dtsi | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap3-igep.dtsi b/arch/arm/boot/dts/omap3-igep.dtsi
> index 125fe00..c02e3c0 100644
> --- a/arch/arm/boot/dts/omap3-igep.dtsi
> +++ b/arch/arm/boot/dts/omap3-igep.dtsi
> @@ -27,6 +27,20 @@
> };
>
> &omap3_pmx_core {
> + uart1_pins: pinmux_uart1_pins {
> + pinctrl-single,pins = <
> + 0x152 0x100 /* uart1_rx.uart1_rx INPUT | MODE0 */
> + 0x14c 0 /* uart1_tx.uart1_tx OUTPUT | MODE0 */
> + >;
> + };
> +
> + uart2_pins: pinmux_uart2_pins {
> + pinctrl-single,pins = <
> + 0x14a 0x100 /* uart2_rx.uart2_rx INPUT | MODE0 */
> + 0x148 0 /* uart2_tx.uart2_tx OUTPUT | MODE0 */
> + >;
> + };
> +
> uart3_pins: pinmux_uart3_pins {
> pinctrl-single,pins = <
> 0x16e 0x100 /* uart3_rx.uart3_rx INPUT | MODE0 */
> @@ -77,6 +91,16 @@
> status = "disabled";
> };
>
> +&uart1 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart1_pins>;
> +};
> +
> +&uart2 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart2_pins>;
> +};
> +
> &uart3 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart3_pins>;
>
That looks good to me. I'll apply it on top of javier's series for 3.9.
Thanks,
Benoit
next prev parent reply other threads:[~2012-12-12 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 15:33 [PATCH] arm: dts: Add uart1 and uart2 to igep boards Matthias Brugger
2012-12-12 16:09 ` Benoit Cousson [this message]
2013-01-26 15:16 ` Matthias Brugger
[not found] ` <CABuKBeJsHCq98Pe-BwPajbQ+2OLQpwrbtVTJe=j9thPDQCCBrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-26 15:56 ` Javier Martinez Canillas
2013-02-15 9:35 ` Matthias Brugger
[not found] ` <CABuKBeJsg_P=aDr0s9iVOD+7YTNoVUFQJCJymJyJ7NqXHUBzKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-15 10:03 ` Cousson, Benoit
2013-03-02 1:52 ` Javier Martinez Canillas
2013-03-13 16:41 ` Benoit Cousson
2013-03-13 17:58 ` Javier Martinez Canillas
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=50C8AC3C.9020908@ti.com \
--to=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=eballetbo@gmail.com \
--cc=ebutera@gmail.com \
--cc=elezegarcia@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).