From: kishon <kishon@ti.com>
To: <balbi@ti.com>
Cc: <grant.likely@secretlab.ca>, <rob.herring@calxeda.com>,
<rob@landley.net>, <b-cousson@ti.com>, <tony@atomide.com>,
<linux@arm.linux.org.uk>, <devicetree-discuss@lists.ozlabs.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 8/8] ARM: dts: omap5: add dwc3 core dt data
Date: Wed, 6 Mar 2013 14:25:48 +0530 [thread overview]
Message-ID: <51370494.7090902@ti.com> (raw)
In-Reply-To: <20130305143934.GB12123@arwen.pp.htv.fi>
Hi,
On Tuesday 05 March 2013 08:09 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Mar 05, 2013 at 08:07:03PM +0530, Kishon Vijay Abraham I wrote:
>> Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
>> data file. The information for the entered data node is available @
>> Documentation/devicetree/bindings/usb/dwc3.txt
>>
>> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
>> ---
>> arch/arm/boot/dts/omap5.dtsi | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
>> index c4eb2ec..24dd69f 100644
>> --- a/arch/arm/boot/dts/omap5.dtsi
>> +++ b/arch/arm/boot/dts/omap5.dtsi
>> @@ -514,6 +514,13 @@
>> #size-cells = <1>;
>> utmi-mode = <2>;
>> ranges;
>> + dwc3@4a030000 {
>> + compatible = "synopsys,dwc3";
>> + reg = <0x4a030000 0x1000>;
>> + interrupts = <0 92 4>;
>> + usb-phy = <&usb2_phy>, <&usb3_phy>;
>> + tx-fifo-resize;
>
> I think this should be merged with previous patch. Also, we need to
> check whether tx-fifo-resize is needed with ES2 or not ;-)
yeah. ES2 works without tx-fifo-resize.
Thanks
Kishon
next prev parent reply other threads:[~2013-03-06 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 14:36 [PATCH v2 0/8] ARM: dts: omap: Add dts data for USB Kishon Vijay Abraham I
2013-03-05 14:36 ` [PATCH v2 1/8] ARM: dts: omap: Add omap control usb data Kishon Vijay Abraham I
2013-03-05 14:36 ` [PATCH v2 2/8] ARM: dts: omap: Add omap-usb2 dt data Kishon Vijay Abraham I
2013-03-05 14:36 ` [PATCH v2 3/8] ARM: dts: omap: Add usb_otg and glue data Kishon Vijay Abraham I
2013-03-05 14:36 ` [PATCH v2 4/8] ARM: dts: omap5: Add omap control usb data Kishon Vijay Abraham I
2013-03-05 14:37 ` [PATCH v2 5/8] ARM: dts: omap5: Add ocp2scp data Kishon Vijay Abraham I
2013-03-05 14:37 ` [PATCH v2 6/8] ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data Kishon Vijay Abraham I
2013-03-05 14:37 ` [PATCH v2 7/8] ARM: dts: omap5: add dwc3 omap " Kishon Vijay Abraham I
2013-03-05 14:41 ` Sergei Shtylyov
2013-03-05 15:03 ` kishon
2013-03-05 14:37 ` [PATCH v2 8/8] ARM: dts: omap5: add dwc3 core " Kishon Vijay Abraham I
2013-03-05 14:39 ` Felipe Balbi
2013-03-06 8:55 ` kishon [this message]
2013-03-06 9:19 ` Felipe Balbi
2013-03-06 9:21 ` kishon
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=51370494.7090902@ti.com \
--to=kishon@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=tony@atomide.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