linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hzpeterchen@gmail.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v13 06/12] usb: xhci: use bus->sysdev for DMA configuration
Date: Wed, 15 Feb 2017 16:51:27 +0800	[thread overview]
Message-ID: <20170215085127.GA26227@b29397-desktop> (raw)
In-Reply-To: <cb3ee971-6d97-fff1-64f7-1b527559b047@ti.com>

On Wed, Feb 15, 2017 at 10:18:03AM +0200, Roger Quadros wrote:
> Peter,
> 
> On 15/02/17 03:35, Peter Chen wrote:
> > On Tue, Feb 14, 2017 at 01:58:40PM +0100, Arnd Bergmann wrote:
> >> On Tue, Feb 14, 2017 at 1:26 PM, Roger Quadros <rogerq@ti.com> wrote:
> >>> On 14/02/17 13:44, Arnd Bergmann wrote:
> >>>> On Tue, Feb 14, 2017 at 11:36 AM, Roger Quadros <rogerq@ti.com> wrote:
> >>
> >>>>> Why are we using sysdev to read DT property? We should be using the
> >>>>> XHCI device (&pdev->dev) here, no?
> >>>>
> >>>> If I remember correctly, this is one of the cases where pdev does not
> >>>> have a device node attached to it because it was created by the driver
> >>>> of the parent device on the fly in case of dwc3. When you have a pure xhci
> >>>> device in DT, the two pointers are the same.
> >>>
> >>> From drivers/usb/dwc3/host.c
> >>>
> >>>>         if (dwc->usb3_lpm_capable) {
> >>>>                 props[0].name = "usb3-lpm-capable";
> >>>>                 ret = platform_device_add_properties(xhci, props);
> >>>>                 if (ret) {
> >>>>                         dev_err(dwc->dev, "failed to add properties to xHCI\n");
> >>>>                         goto err1;
> >>>>                 }
> >>>>         }
> >>>
> >>> So it is setting the usb3-lpm-capable property into the xhci platform device
> >>> and we should be reading the property from there.
> > 
> > Why dwc3 needs another "snps,usb3_lpm_capable"? Why not using
> > "usb3-lpm-capable" at firmware directly?
> 
> dwc3 is not setting "snps,usb3_lpm_capable" but "usb3-lpm-capable" for the
> xhci platform device.
> 
> What did you mean by firmware? Did you mean something like BIOS?
> At least TI platforms don't use any firmware like BIOS. So dwc3 driver
> needs to create a platform device for xhci on the fly and set the DT properties.
> 

By readying code, the dwc3 calls dwc3_get_properties to set
dwc->usb3_lpm_capable, and at dwc3/host.c, it sets property
"usb3-lpm-capable" according to this flag, why not let common
code xhci-plat.c to get this property from sysdev which is DT
nodes for dwc3?

-- 

Best Regards,
Peter Chen

  reply	other threads:[~2017-02-15  8:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11  1:27 [PATCH v13 00/12] power: add power sequence library Peter Chen
2017-02-11  1:27 ` [PATCH v13 01/12] binding-doc: power: pwrseq-generic: add binding doc for generic " Peter Chen
2017-02-11  1:27 ` [PATCH v13 02/12] power: add " Peter Chen
2017-02-11  1:27 ` [PATCH v13 03/12] usb: separate out sysdev pointer from usb_bus Peter Chen
2017-02-11  1:27 ` [PATCH v13 04/12] usb: chipidea: use bus->sysdev for DMA configuration Peter Chen
2017-02-11  1:27 ` [PATCH v13 05/12] usb: ehci: fsl: " Peter Chen
2017-02-11  1:27 ` [PATCH v13 06/12] usb: xhci: " Peter Chen
2017-02-13  8:25   ` Alexander Sverdlin
2017-02-14  5:33   ` Vivek Gautam
2017-02-14 10:36   ` Roger Quadros
2017-02-14 11:44     ` Arnd Bergmann
2017-02-14 12:26       ` Roger Quadros
2017-02-14 12:58         ` Arnd Bergmann
2017-02-15  1:35           ` Peter Chen
2017-02-15  8:18             ` Roger Quadros
2017-02-15  8:51               ` Peter Chen [this message]
2017-02-15 10:10                 ` Roger Quadros
2017-02-15 11:51                   ` Felipe Balbi
2017-02-16  1:23                     ` Peter Chen
2017-02-11  1:27 ` [PATCH v13 07/12] usb: ehci: " Peter Chen
2017-02-11  1:27 ` [PATCH v13 08/12] binding-doc: usb: usb-device: add optional properties for power sequence Peter Chen
2017-02-11  1:27 ` [PATCH v13 09/12] usb: core: add power sequence handling for USB devices Peter Chen
2017-02-11  1:27 ` [PATCH v13 10/12] ARM: dts: imx6qdl: Enable usb node children with <reg> Peter Chen
2017-02-11  1:27 ` [PATCH v13 11/12] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2017-02-11  1:27 ` [PATCH v13 12/12] ARM: dts: imx6q-evi: Fix onboard hub reset line Peter Chen
2017-02-13 12:22 ` [PATCH v13 00/12] power: add power sequence library Rafael J. Wysocki
2017-02-14 10:21 ` Roger Quadros
2017-02-15  1:38   ` Peter Chen
2017-05-16 17:28     ` Krzysztof Kozlowski
2017-05-17  1:18       ` Peter Chen

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=20170215085127.GA26227@b29397-desktop \
    --to=hzpeterchen@gmail.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).