From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: at91: add Acme Systems Aria G25 board
Date: Thu, 18 Apr 2013 12:13:06 +0200 [thread overview]
Message-ID: <516FC732.9080109@atmel.com> (raw)
In-Reply-To: <516FB671.2030706@atmel.com>
On 04/18/2013 11:01 AM, Nicolas Ferre :
> On 04/04/2013 07:03 PM, Douglas Gilbert :
[..]
>> The lack of use of uart1 is for my own, private reasons.
>> I think it would be more generally useful to show uart1's
>> definition and disable it as shown in the attached patch
>> fragment.
>
> Well, if uart1 is available on Aria board, I should enable it! If you do
> not want it on your own design, you must modify the .dts yourself. So I
> plan to have an "okay" status on it (and move the definition itself to
> the generic .dtsi).
Update: I have just checked the ACME website and both UART0 and UART1
pins are expected to be used as GPIOs. So maybe we should mark them as
"disabled":
+ /*
+ * UART1 pins are marked as GPIO on Aria
+ * documentation: change to "okay" if you need
+ * an additional serial port
+ */
+ uart0: serial at f8040000 {
+ status = "disabled";
+ };
+
+ uart1: serial at f8044000 {
+ status = "disabled";
+ };
(uart0 definition moved to at91sam9x5.dtsi)
What do you think?
[..]
Bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: <dgilbert@interlog.com>, <robertcnelson@gmail.com>
Cc: <jhovold@gmail.com>, <linux-kernel@vger.kernel.org>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
<linux-arm-kernel@lists.infradead.org>,
"Sergio Tanzilli" <tanzilli@acmesystems.it>
Subject: Re: [PATCH v3] ARM: at91: add Acme Systems Aria G25 board
Date: Thu, 18 Apr 2013 12:13:06 +0200 [thread overview]
Message-ID: <516FC732.9080109@atmel.com> (raw)
In-Reply-To: <516FB671.2030706@atmel.com>
On 04/18/2013 11:01 AM, Nicolas Ferre :
> On 04/04/2013 07:03 PM, Douglas Gilbert :
[..]
>> The lack of use of uart1 is for my own, private reasons.
>> I think it would be more generally useful to show uart1's
>> definition and disable it as shown in the attached patch
>> fragment.
>
> Well, if uart1 is available on Aria board, I should enable it! If you do
> not want it on your own design, you must modify the .dts yourself. So I
> plan to have an "okay" status on it (and move the definition itself to
> the generic .dtsi).
Update: I have just checked the ACME website and both UART0 and UART1
pins are expected to be used as GPIOs. So maybe we should mark them as
"disabled":
+ /*
+ * UART1 pins are marked as GPIO on Aria
+ * documentation: change to "okay" if you need
+ * an additional serial port
+ */
+ uart0: serial@f8040000 {
+ status = "disabled";
+ };
+
+ uart1: serial@f8044000 {
+ status = "disabled";
+ };
(uart0 definition moved to at91sam9x5.dtsi)
What do you think?
[..]
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2013-04-18 10:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 14:59 [GIT PULL] at91: DT changes for 3.10 #2 Nicolas Ferre
2013-03-29 14:59 ` Nicolas Ferre
2013-04-02 18:49 ` Olof Johansson
2013-04-02 18:49 ` Olof Johansson
2013-04-03 7:45 ` Nicolas Ferre
2013-04-03 7:45 ` Nicolas Ferre
2013-04-04 9:37 ` Nicolas Ferre
2013-04-04 9:37 ` Nicolas Ferre
2013-04-04 17:19 ` Olof Johansson
2013-04-04 17:19 ` Olof Johansson
2013-04-08 11:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-08 11:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-04 15:42 ` [PATCH v3] ARM: at91: add Acme Systems Aria G25 board Nicolas Ferre
2013-04-04 15:42 ` Nicolas Ferre
2013-04-04 17:03 ` Douglas Gilbert
2013-04-04 17:03 ` Douglas Gilbert
2013-04-18 9:01 ` Nicolas Ferre
2013-04-18 9:01 ` Nicolas Ferre
2013-04-18 10:13 ` Nicolas Ferre [this message]
2013-04-18 10:13 ` Nicolas Ferre
2013-04-04 16:59 ` [GIT PULL] at91: DT changes for 3.10 #3 Nicolas Ferre
2013-04-04 16:59 ` Nicolas Ferre
2013-04-09 8:17 ` Nicolas Ferre
2013-04-09 8:17 ` Nicolas Ferre
2013-04-09 9:47 ` Arnd Bergmann
2013-04-09 9:47 ` Arnd Bergmann
2013-04-09 10:49 ` Arnd Bergmann
2013-04-09 10:49 ` Arnd Bergmann
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=516FC732.9080109@atmel.com \
--to=nicolas.ferre@atmel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.