mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [RFC usb-next v5 1/3] dt-bindings: usb: add the documentation for USB root-hub
Date: Thu, 19 Oct 2017 11:54:29 +0200	[thread overview]
Message-ID: <d154baad-45c6-2665-6515-b151609e4605@baylibre.com> (raw)
In-Reply-To: <CAK8P3a0hFF-gMa4UWMXh-28=scF-8cnzPv-Sa11PzyvgMYAkQw@mail.gmail.com>

On 18/10/2017 11:05, Arnd Bergmann wrote:
> On Tue, Oct 17, 2017 at 11:19 PM, Martin Blumenstingl
> <martin.blumenstingl@googlemail.com> wrote:
>>> Ok, very good!
>>>
>>>> is there anything else you want me to test?
>>>
>>> What about the same dtb when run on a kernel without your
>>> patch series? Does that work as well, or are your patches
>>> required to make it work?
>>
>> this is the only device I have which uses devicetree and a xHCI
>> controller. I can test it with a dwc2 based device though if you want
> 
> Does dwc2 also use separate nodes for the roothub? From your
> description it sounds like it would not be affected by your patch.
> 
> To rephrase what I'm interested in, can you check that with your
> patch series, we correctly associate a device node in DT with the
> struct device in the kernel both with and without the optional
> roothub node in the dtb?
> 
> Since you used a dtb that already listed an endpoint device below
> an xhci, that would answer my earlier question of whether it worked
> before your patch series, and you tested that it still works with your
> patches applied and the roothub node added in the dtb.  Now we
> just need to make sure we don't break existing dtb files that don't
> have the roothub node but do have endpoint device nodes.
> 
>        Arnd
> 
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
> 

Hi Arnd,

I tested in the same conditions :
- On Odroid-C2 using DWC2, but not using the roothub functionnality
- patch v6 applied
- node for on-board hub
- printk in usb core

And it works :
[    8.767964] usb 1-1: of_node /soc/usb at c9100000/hub at 1 parent /soc/usb at c9100000
[    8.955901] usb 1-1: new high-speed USB device number 2 using dwc2
[    9.165641] hub 1-1:1.0: USB hub found
[    9.165939] hub 1-1:1.0: 4 ports detected

Neil

  reply	other threads:[~2017-10-19  9:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 21:17 [RFC usb-next v5 0/3] initialize (multiple) PHYs on the roothub Martin Blumenstingl
2017-10-08 21:17 ` [RFC usb-next v5 1/3] dt-bindings: usb: add the documentation for USB root-hub Martin Blumenstingl
2017-10-09 10:24   ` Arnd Bergmann
2017-10-12 20:56     ` Martin Blumenstingl
2017-10-12 21:17       ` Alan Stern
2017-10-12 21:35         ` Martin Blumenstingl
2017-10-13 14:15           ` Alan Stern
2017-10-17 21:02             ` Martin Blumenstingl
2017-10-13  7:37       ` Arnd Bergmann
2017-10-17 21:00         ` Martin Blumenstingl
2017-10-17 21:10           ` Arnd Bergmann
2017-10-17 21:19             ` Martin Blumenstingl
2017-10-18  9:05               ` Arnd Bergmann
2017-10-19  9:54                 ` Neil Armstrong [this message]
2017-10-19 21:25                 ` Martin Blumenstingl
2017-10-19 22:10                   ` Arnd Bergmann
2017-10-23 21:36                     ` Martin Blumenstingl
2017-10-08 21:17 ` [RFC usb-next v5 2/3] usb: core: add a wrapper for the USB PHYs on the root-hub Martin Blumenstingl
2017-10-09 17:16   ` Alan Stern
2017-10-12 21:00     ` Martin Blumenstingl
2017-10-12 21:08   ` Martin Blumenstingl
2017-10-08 21:17 ` [RFC usb-next v5 3/3] usb: core: hcd: integrate the PHY roothub wrapper Martin Blumenstingl
2017-10-09 17:18   ` Alan Stern
2017-10-12 21:05     ` Martin Blumenstingl
2017-10-13 14:07       ` Alan Stern
2017-10-17 21:05         ` Martin Blumenstingl

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=d154baad-45c6-2665-6515-b151609e4605@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=linus-amlogic@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

all inboxes | Powered by JetHome®