From: Frank Rowand <frowand.list@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] tty: serial: msm_serial: Use DT aliases
Date: Fri, 07 Nov 2014 13:35:45 -0800 [thread overview]
Message-ID: <545D3B31.3030309@gmail.com> (raw)
In-Reply-To: <2747100.M77UGx4AmB@wuerfel>
On 11/7/2014 1:47 AM, Arnd Bergmann wrote:
> On Thursday 06 November 2014 22:42:47 Frank Rowand wrote:
>> This same change is also needed in:
>>
>> qcom-ipq8064.dtsi
>> qcom-msm8960.dtsi
>> qcom-apq8084.dtsi
>> qcom-apq8064.dtsi
>> qcom-msm8660.dtsi
>>
>> but I did not want to just blindly apply those changes without testing.
>>
>
> Is there only one uart on each of these?
>
> If not, it would be better to put the aliases in the board specific file,
> pointing to whichever ports are in use, in the order that makes sense
> for that board.
Good point, thanks for bringing it up.
Your comment made me verify that the board dts files can override the
aliases from the included .dtsi. So not a problem to have a default
set of aliases in the .dtsi files.
-Frank
next prev parent reply other threads:[~2014-11-07 21:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 0:33 [PATCH] tty: serial: msm_serial: Use DT aliases Stephen Boyd
2014-11-07 4:44 ` Frank Rowand
2014-11-10 23:53 ` Stephen Boyd
2014-11-11 2:20 ` Frank Rowand
2014-11-11 2:23 ` Stephen Boyd
2014-11-07 6:40 ` Frank Rowand
2014-11-07 6:42 ` Frank Rowand
2014-11-07 9:47 ` Arnd Bergmann
2014-11-07 21:35 ` Frank Rowand [this message]
2014-11-08 19:25 ` Arnd Bergmann
2014-11-10 18:54 ` Kevin Hilman
2014-11-10 19:42 ` Stephen Boyd
2014-11-11 1:56 ` Frank Rowand
2014-11-11 2:07 ` Stephen Boyd
2014-11-11 3:20 ` Frank Rowand
2014-11-12 18:14 ` Frank Rowand
2014-11-13 19:31 ` Stephen Boyd
2014-11-14 0:46 ` Frank Rowand
2014-11-14 0:59 ` Stephen Boyd
2014-11-14 17:43 ` Kevin Hilman
2014-11-14 18:33 ` Stephen Boyd
2014-11-11 15:31 ` Kevin Hilman
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=545D3B31.3030309@gmail.com \
--to=frowand.list@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).