From: r.sricharan@ti.com (Sricharan R)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] ARM: dts: omap5-uevm: Add USB Host support
Date: Fri, 7 Jun 2013 11:38:00 +0530 [thread overview]
Message-ID: <51B178C0.1040901@ti.com> (raw)
In-Reply-To: <20130606184617.GA25579@kahuna>
On Friday 07 June 2013 12:16 AM, Nishanth Menon wrote:
> On 23:21-20130606, Sricharan R wrote:
>> Hi,
>> On Wednesday 05 June 2013 07:27 PM, Nishanth Menon wrote:
>>> On 12:16-20130605, Sricharan R wrote:
>>>> From: Roger Quadros <rogerq@ti.com>
>>> [...]
>>>> diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
>>>> index 843a001..cf862df 100644
>>>> --- a/arch/arm/boot/dts/omap5-uevm.dts
>>>> +++ b/arch/arm/boot/dts/omap5-uevm.dts
>>> <snip>
>>>> + /* hsusb2_phy is clocked by FREF_CLK1 i.e. auxclk1 */
>>>> + clock_alias {
>>>> + clock-name = "auxclk1_ck";
>>>> + clock-alias = "main_clk";
>>> is'nt this better to use with clock node?
>> Roger was suggesting to remove this for now. Postedhen
>> V2 following that.
>> Are you suggesting to go with your clock-binding patch ?
> you cannot. Mike has already rejected that approach and I have dropped
> that series and wont be following up.
> See discussion https://patchwork.kernel.org/patch/2541331/
>
> instead the new approach being discussed
> https://patchwork.kernel.org/patch/2657351/ and related discussions is
> the way to go.
>
> That said, it practically blocks introduction of all code that depend on
> dts nodes :(, no matter how I dont like being blocked and my many series
> delayed, I believe Mike, Tero, Rajendra are doing the right architecture
> and we should wait for it's upstream introduction.
>
> That is just my 2 cents.
>
Thanks for the details. So dropping the alias for now, should be fine.
Regards,
Sricharan
next prev parent reply other threads:[~2013-06-07 6:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 6:46 [PATCH 0/4] ARM: dts: omap5: Cleanup and updates for DT files Sricharan R
2013-06-05 6:46 ` [PATCH 1/4] ARM: dts: omap5: Rename omap5-evm to omap5-uevm Sricharan R
2013-06-05 6:50 ` Sricharan R
2013-06-05 6:46 ` [PATCH 2/4] ARM: dts: omap5-uevm: Add USB Host support Sricharan R
2013-06-05 7:59 ` Florian Vaussard
2013-06-05 9:12 ` Sricharan R
2013-06-05 12:15 ` Florian Vaussard
2013-06-05 10:32 ` Roger Quadros
2013-06-05 11:50 ` Sricharan R
2013-06-05 13:57 ` Nishanth Menon
2013-06-06 17:51 ` Sricharan R
2013-06-06 18:46 ` Nishanth Menon
2013-06-07 6:08 ` Sricharan R [this message]
2013-06-05 6:46 ` [PATCH 3/4] ARM: dts: omap5-uevm: Add LED support for uEVM blue LED Sricharan R
2013-06-05 17:04 ` Dan Murphy
2013-06-06 17:52 ` Sricharan R
2013-06-05 6:46 ` [PATCH 4/4] ARM: dts: omap5-uevm: Add uart pinctrl data Sricharan R
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=51B178C0.1040901@ti.com \
--to=r.sricharan@ti.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 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).