From: George Cherian <george.cherian@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux@arm.linux.org.uk,
galak@codeaurora.org, ijc+devicetree@hellion.org.uk,
mark.rutland@arm.com, pawel.moll@arm.com, robh+dt@kernel.org,
bcousson@baylibre.com, ezequiel@vanguardiasur.com.ar,
bigeasy@linutronix.de, yegorslists@googlemail.com, balbi@ti.com
Subject: Re: [RFC PATCH] ARM: dts: am33xx: Re-arrange the USB dt to reflect the h/w configuration
Date: Thu, 15 May 2014 11:38:36 +0530 [thread overview]
Message-ID: <537459E4.5060203@ti.com> (raw)
In-Reply-To: <20140514215034.GL27426@atomide.com>
Hi Tony,
On 5/15/2014 3:20 AM, Tony Lindgren wrote:
> * George Cherian <george.cherian@ti.com> [140508 23:34]:
>> Re arrange the USB dt for AM33xx to take it a bit closer
>> to the hardware configuration.
>>
>> The USBSS is designed as follows
>>
>> USB control Module 0x44e10_0620
>>
>> USBSS 0x4740_0000
>>
>> USB0 0x4740_1000
>> USB0_PHY 0x4740_1300
>> USB0_CORE 0x4740_1400
>>
>> USB1 0x4740_1800
>> USB1_PHY 0x4740_1b00
>> USB1_CORE 0x4740_1c00
>>
>> CPPI DMA Controller 0x4740_2000
>> CPPI DMA Scheduler 0x4740_3000
>> Queue Manager 0x4740_4000
>>
>> So model the DT as follows
>> USBSS {
>> usb_ctrl_mod: {
>> 0x44e10_0620
>> }
>> usb0: {
>> 0x4740_1000
>> 0x4740_1400
>> }
>> usb0_phy:{
>> 0x4740_1300
>> }
>> usb1:{
>> 0x4740_1800
>> 0x4740_1c00
>> }
>> usb1_phy: {
>> 0x4740_1b00
>> }
>> cppi41dma: {
>> 0x4740_2000
>> 0x4740_3000
>> 0x4740_4000
>> }
>> }
> Is this just a cosmetic change or is this trying to workaround
> some edma related init order issue?
Please ignore this patch. Was trying to workaround some dma and phy
related issues.
The same got fixed with following
http://www.spinics.net/lists/linux-usb/msg107244.html
>
> Regards,
>
> Tony
--
-George
WARNING: multiple messages have this Message-ID (diff)
From: george.cherian@ti.com (George Cherian)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: dts: am33xx: Re-arrange the USB dt to reflect the h/w configuration
Date: Thu, 15 May 2014 11:38:36 +0530 [thread overview]
Message-ID: <537459E4.5060203@ti.com> (raw)
In-Reply-To: <20140514215034.GL27426@atomide.com>
Hi Tony,
On 5/15/2014 3:20 AM, Tony Lindgren wrote:
> * George Cherian <george.cherian@ti.com> [140508 23:34]:
>> Re arrange the USB dt for AM33xx to take it a bit closer
>> to the hardware configuration.
>>
>> The USBSS is designed as follows
>>
>> USB control Module 0x44e10_0620
>>
>> USBSS 0x4740_0000
>>
>> USB0 0x4740_1000
>> USB0_PHY 0x4740_1300
>> USB0_CORE 0x4740_1400
>>
>> USB1 0x4740_1800
>> USB1_PHY 0x4740_1b00
>> USB1_CORE 0x4740_1c00
>>
>> CPPI DMA Controller 0x4740_2000
>> CPPI DMA Scheduler 0x4740_3000
>> Queue Manager 0x4740_4000
>>
>> So model the DT as follows
>> USBSS {
>> usb_ctrl_mod: {
>> 0x44e10_0620
>> }
>> usb0: {
>> 0x4740_1000
>> 0x4740_1400
>> }
>> usb0_phy:{
>> 0x4740_1300
>> }
>> usb1:{
>> 0x4740_1800
>> 0x4740_1c00
>> }
>> usb1_phy: {
>> 0x4740_1b00
>> }
>> cppi41dma: {
>> 0x4740_2000
>> 0x4740_3000
>> 0x4740_4000
>> }
>> }
> Is this just a cosmetic change or is this trying to workaround
> some edma related init order issue?
Please ignore this patch. Was trying to workaround some dma and phy
related issues.
The same got fixed with following
http://www.spinics.net/lists/linux-usb/msg107244.html
>
> Regards,
>
> Tony
--
-George
WARNING: multiple messages have this Message-ID (diff)
From: George Cherian <george.cherian@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <linux@arm.linux.org.uk>,
<galak@codeaurora.org>, <ijc+devicetree@hellion.org.uk>,
<mark.rutland@arm.com>, <pawel.moll@arm.com>,
<robh+dt@kernel.org>, <bcousson@baylibre.com>,
<ezequiel@vanguardiasur.com.ar>, <bigeasy@linutronix.de>,
<yegorslists@googlemail.com>, <balbi@ti.com>
Subject: Re: [RFC PATCH] ARM: dts: am33xx: Re-arrange the USB dt to reflect the h/w configuration
Date: Thu, 15 May 2014 11:38:36 +0530 [thread overview]
Message-ID: <537459E4.5060203@ti.com> (raw)
In-Reply-To: <20140514215034.GL27426@atomide.com>
Hi Tony,
On 5/15/2014 3:20 AM, Tony Lindgren wrote:
> * George Cherian <george.cherian@ti.com> [140508 23:34]:
>> Re arrange the USB dt for AM33xx to take it a bit closer
>> to the hardware configuration.
>>
>> The USBSS is designed as follows
>>
>> USB control Module 0x44e10_0620
>>
>> USBSS 0x4740_0000
>>
>> USB0 0x4740_1000
>> USB0_PHY 0x4740_1300
>> USB0_CORE 0x4740_1400
>>
>> USB1 0x4740_1800
>> USB1_PHY 0x4740_1b00
>> USB1_CORE 0x4740_1c00
>>
>> CPPI DMA Controller 0x4740_2000
>> CPPI DMA Scheduler 0x4740_3000
>> Queue Manager 0x4740_4000
>>
>> So model the DT as follows
>> USBSS {
>> usb_ctrl_mod: {
>> 0x44e10_0620
>> }
>> usb0: {
>> 0x4740_1000
>> 0x4740_1400
>> }
>> usb0_phy:{
>> 0x4740_1300
>> }
>> usb1:{
>> 0x4740_1800
>> 0x4740_1c00
>> }
>> usb1_phy: {
>> 0x4740_1b00
>> }
>> cppi41dma: {
>> 0x4740_2000
>> 0x4740_3000
>> 0x4740_4000
>> }
>> }
> Is this just a cosmetic change or is this trying to workaround
> some edma related init order issue?
Please ignore this patch. Was trying to workaround some dma and phy
related issues.
The same got fixed with following
http://www.spinics.net/lists/linux-usb/msg107244.html
>
> Regards,
>
> Tony
--
-George
next prev parent reply other threads:[~2014-05-15 6:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 6:31 [RFC PATCH] ARM: dts: am33xx: Re-arrange the USB dt to reflect the h/w configuration George Cherian
2014-05-09 6:31 ` George Cherian
2014-05-09 6:31 ` George Cherian
[not found] ` <1399617068-19826-1-git-send-email-george.cherian-l0cyMroinI0@public.gmane.org>
2014-05-14 21:50 ` Tony Lindgren
2014-05-14 21:50 ` Tony Lindgren
2014-05-14 21:50 ` Tony Lindgren
2014-05-15 6:08 ` George Cherian [this message]
2014-05-15 6:08 ` George Cherian
2014-05-15 6:08 ` George Cherian
2014-05-18 0:09 ` Ezequiel Garcia
2014-05-18 0:09 ` Ezequiel Garcia
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=537459E4.5060203@ti.com \
--to=george.cherian@ti.com \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=bigeasy@linutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.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 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.