From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: shmobile: r8a7790: link PCI USB devices to USB PHY
Date: Mon, 26 May 2014 22:46:17 +0000 [thread overview]
Message-ID: <5383C439.1080808@cogentembedded.com> (raw)
In-Reply-To: <CANqRtoT+xKmK7wkayiD9yCmUqFNKWxpeSgkGTiCqc+THYE0sVw@mail.gmail.com>
Hello.
On 05/27/2014 02:36 AM, Magnus Damm wrote:
>> Describe the PCI USB devices that are behind the PCI bridges, adding necessary
>> links to the USB PHY device.
>> Based on the original work by Ben Dooks <ben.dooks@codethink.co.uk>.
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> ---
>> This patch is against 'renesas-devel-v3.15-rc7-20140526' tag of Simon Horman's
>> 'renesas.git' repo plus R8A7790/Lager PCI and USB PHY support patches posted
>> before. The patch requires the internal PCI DT support, USB PHY driver, and
>> USB HCD generic PHY support (also already posted) in order to work.
>> Changes in version 2:
>> - renamed the PCI OHCI/EHCI device nodes to comply with the PCI binding;
>> - changed the PHY specifier in the PCI#2 node to reflect that channel #1 support
>> was dropped;
>> - resolved rejects, refreshed the patch.
>> arch/arm/boot/dts/r8a7790.dtsi | 28 ++++++++++++++++++++++++++++
>> 1 file changed, 28 insertions(+)
>> Index: renesas/arch/arm/boot/dts/r8a7790.dtsi
>> =================================>> --- renesas.orig/arch/arm/boot/dts/r8a7790.dtsi
>> +++ renesas/arch/arm/boot/dts/r8a7790.dtsi
>> @@ -919,6 +919,20 @@
>> interrupt-map = <0x0000 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH
>> 0x0800 0 0 1 &gic 0 108 IRQ_TYPE_LEVEL_HIGH
>> 0x1000 0 0 2 &gic 0 108 IRQ_TYPE_LEVEL_HIGH>;
>> +
>> + usb@0,1 {
>> + reg = <0x800 0 0 0 0>;
>> + device_type = "pci";
>> + phys = <&usbphy 0 0>;
>> + phy-names = "usb";
>> + };
>> +
>> + usb@0,2 {
>> + reg = <0x1000 0 0 0 0>;
>> + device_type = "pci";
>> + phys = <&usbphy 0 0>;
>> + phy-names = "usb";
>> + };
>> };
>>
>> pci1: pci@ee0b0000 {
>> @@ -955,5 +969,19 @@
>> interrupt-map = <0x0000 0 0 1 &gic 0 113 IRQ_TYPE_LEVEL_HIGH
>> 0x0800 0 0 1 &gic 0 113 IRQ_TYPE_LEVEL_HIGH
>> 0x1000 0 0 2 &gic 0 113 IRQ_TYPE_LEVEL_HIGH>;
>> +
>> + usb@0,1 {
>> + reg = <0x800 0 0 0 0>;
>> + device_type = "pci";
>> + phys = <&usbphy 1 0>;
>> + phy-names = "usb";
>> + };
>> +
>> + usb@0,2 {
>> + reg = <0x1000 0 0 0 0>;
>> + device_type = "pci";
>> + phys = <&usbphy 1 0>;
>> + phy-names = "usb";
>> + };
>> };
>> };
> Hi Sergei,
> Above I see two hunks of DTS code but my r8a7790 data sheet contains
> three USB PCI devices. Perhaps my understanding is wrong, or may there
You probably wanted to say 6 (OHCI and EHCI are 2 different PCI devices).
> is some other patch available to enable all USB PCI devices included
> in the SoC?
This patch doesn't enable USB devices, it just links them to the PHY where
it makes sense (for USB channel #1 it doesn't).
> Thanks,
> / magnus
WBR, Sergei
next prev parent reply other threads:[~2014-05-26 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 22:17 [PATCH v2] ARM: shmobile: r8a7790: link PCI USB devices to USB PHY Sergei Shtylyov
2014-05-26 22:36 ` Magnus Damm
2014-05-26 22:46 ` Sergei Shtylyov [this message]
2014-05-27 0:41 ` Magnus Damm
2014-05-28 21:51 ` Sergei Shtylyov
2014-06-04 20:03 ` Sergei Shtylyov
2014-06-05 0:43 ` Magnus Damm
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=5383C439.1080808@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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).