From: hzpeterchen@gmail.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 5/6] usb: chipidea: let chipidea core device of_node equal's glue layer device of_node
Date: Wed, 10 Aug 2016 11:11:46 +0800 [thread overview]
Message-ID: <20160810031146.GE1879@shlinux2> (raw)
In-Reply-To: <147078813636.20133.1120685098868481913@sboyd-linaro>
On Tue, Aug 09, 2016 at 05:15:36PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-08-08 01:52:10)
> > From: Peter Chen <peter.chen@freescale.com>
> >
> > At device tree, we have no device node for chipidea core,
> > the glue layer's node is the parent node for host and udc
> > device. But in related driver, the parent device is chipidea
> > core. So, in order to let the common driver get parent's node,
> > we let the core's device node equals glue layer device node.
> >
> > Signed-off-by: Peter Chen <peter.chen@freescale.com>
> > Tested-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
> > Tested-by Joshua Clayton <stillcompiling@gmail.com>
> > ---
> > drivers/usb/chipidea/core.c | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
> > index 69426e6..b189dc7 100644
> > --- a/drivers/usb/chipidea/core.c
> > +++ b/drivers/usb/chipidea/core.c
> > @@ -954,6 +954,15 @@ static int ci_hdrc_probe(struct platform_device *pdev)
> > dev_err(dev, "unable to init phy: %d\n", ret);
> > return ret;
> > }
> > + /*
> > + * At device tree, we have no device node for chipidea core,
> > + * the glue layer's node is the parent node for host and udc
> > + * device. But in related driver, the parent device is chipidea
> > + * core. So, in order to let the common driver get parent's node,
> > + * we let the core's device node equals glue layer's node.
> > + */
> > + if (dev->parent && dev->parent->of_node)
> > + dev->of_node = dev->parent->of_node;
>
> Can this be done earlier? Perhaps after hw_device_init() in this probe
> routine? That would allow me to remove the awkward parent searching in
> my ULPI DT awareness patch.
The reason why I locate it there is to avoid "goto label" for error
path during PHY's get and initialization operation.
Ok, to simplify your work, I will change it at next version.
--
Best Regards,
Peter Chen
next prev parent reply other threads:[~2016-08-10 3:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 8:52 [PATCH v5 0/6] power: add power sequence library Peter Chen
2016-08-08 8:52 ` [PATCH v5 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic " Peter Chen
2016-08-08 8:52 ` [PATCH v5 2/6] power: add " Peter Chen
2016-08-09 0:25 ` Matthias Kaehlcke
2016-08-08 8:52 ` [PATCH v5 3/6] binding-doc: usb: usb-device: add optional properties for power sequence Peter Chen
2016-08-08 8:52 ` [PATCH v5 4/6] usb: core: add power sequence handling for USB devices Peter Chen
2016-08-08 8:52 ` [PATCH v5 5/6] usb: chipidea: let chipidea core device of_node equal's glue layer device of_node Peter Chen
2016-08-10 0:15 ` Stephen Boyd
2016-08-10 3:11 ` Peter Chen [this message]
2016-08-10 9:00 ` Jun Li
2016-08-10 9:19 ` Peter Chen
2016-08-08 8:52 ` [PATCH v5 6/6] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2016-08-09 23:33 ` Joshua Clayton
2016-08-10 3:02 ` Peter Chen
2016-08-11 16:40 ` [PATCHES] ARM: dts: update udoo and evi hubs to use pwrseq Joshua Clayton
2016-08-11 16:40 ` [PATCH 1/3] ARM: dts: imx6qdl: Enable usb node children with <reg> Joshua Clayton
2016-08-11 16:40 ` [PATCH 2/3] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Joshua Clayton
2016-08-11 16:40 ` [PATCH 3/3] ARM: dts: imx6q-evi: Fix onboard hub reset line Joshua Clayton
2016-08-12 3:11 ` Peter Chen
2016-08-12 15:20 ` Joshua Clayton
2016-08-12 3:09 ` [PATCHES] ARM: dts: update udoo and evi hubs to use pwrseq 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=20160810031146.GE1879@shlinux2 \
--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).