From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Boris BREZILLON <b.brezillon@overkiz.com>
Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH] ARM: at91/dt: fix macb pinctrl_macb_rmii_mii_alt definition
Date: Fri, 24 May 2013 10:52:31 +0200 [thread overview]
Message-ID: <519F2A4F.8080008@atmel.com> (raw)
In-Reply-To: <1369324881-31428-1-git-send-email-b.brezillon@overkiz.com>
On 23/05/2013 18:01, Boris BREZILLON :
> The PA24 pin is wrongly assigned to peripheral B.
> In the current config there is 2 ETX3 pins (PA11 and PA24) and
> no ETXER pin (PA22).
>
> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz.com>
Nice catch!
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
and stacked on at91-3.10-fixes and add the stable tag #3.8+
Thanks, bye.
> ---
> arch/arm/boot/dts/at91sam9260.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/at91sam9260.dtsi b/arch/arm/boot/dts/at91sam9260.dtsi
> index 70b5ccb..84c4bef 100644
> --- a/arch/arm/boot/dts/at91sam9260.dtsi
> +++ b/arch/arm/boot/dts/at91sam9260.dtsi
> @@ -264,7 +264,7 @@
> atmel,pins =
> <0 10 0x2 0x0 /* PA10 periph B */
> 0 11 0x2 0x0 /* PA11 periph B */
> - 0 24 0x2 0x0 /* PA24 periph B */
> + 0 22 0x2 0x0 /* PA22 periph B */
> 0 25 0x2 0x0 /* PA25 periph B */
> 0 26 0x2 0x0 /* PA26 periph B */
> 0 27 0x2 0x0 /* PA27 periph B */
>
--
Nicolas Ferre
prev parent reply other threads:[~2013-05-24 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 16:01 [PATCH] ARM: at91/dt: fix macb pinctrl_macb_rmii_mii_alt definition Boris BREZILLON
2013-05-24 8:52 ` Nicolas Ferre [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=519F2A4F.8080008@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=b.brezillon@overkiz.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=plagnioj@jcrosoft.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