From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH] musb: sunxi: Ignore VBus errors in host-only mode
Date: Mon, 14 Sep 2015 19:56:55 +0200 [thread overview]
Message-ID: <55F70A67.3020502@redhat.com> (raw)
In-Reply-To: <CADYTM3b3U0iPGiWdnRiXL4WoAjP=_PvZazuArgJgvJ9fJNPV0g@mail.gmail.com>
Hi,
On 14-09-15 19:53, Bin Liu wrote:
<snip>
>>> This is my first time looking at dts handling in drivers, so I might
>>> be completely wrong, but I am thinking that since the controller node
>>> links to the phy node, so the controller node is the parent of the phy
>>> node, so if there is an of api can look it up?
>>
>>
>> If the phy is a child of the controller, then yes this would work,
>> but in the case of sunxi the phy is a built-in mmio mapped peripheral
>> just like the controller, so they sit at the same level and have no
>> parent child relation.
>
> musb_dsps dts is the same.
>
> sun8i-a33.dtsi:
>
> soc {
> usb_otg: {
> phys = <&usbphy 0>;
> }
> usbphy: {
> }
> }
>
> As in the example above, usb_otg node refers to usbphy node, so I am
> wondering if there is an of api to look up the usb_otg properties in
> the usbphy driver.
That would boil down to hardcoding the node name / path compatible
which is not acceptable from a devicetree pov.
Really having to duplicate the dr_mode is not that bad / such big
a deal.
Regards,
Hans
next prev parent reply other threads:[~2015-09-14 17:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 21:25 [PATCH] musb: sunxi: Ignore VBus errors in host-only mode Hans de Goede
2015-08-04 21:35 ` Felipe Balbi
2015-08-04 22:05 ` Hans de Goede
2015-08-04 22:57 ` Felipe Balbi
2015-08-05 13:30 ` Hans de Goede
2015-08-06 8:22 ` [linux-sunxi] " Olliver Schinagl
2015-08-06 14:35 ` Hans de Goede
2015-08-07 8:45 ` Olliver Schinagl
2015-09-04 6:43 ` Olliver Schinagl
2015-09-10 18:23 ` Hans de Goede
2015-09-10 18:30 ` Maxime Ripard
2015-09-10 18:38 ` Hans de Goede
2015-09-14 14:44 ` Bin Liu
2015-09-14 14:59 ` Hans de Goede
2015-09-14 16:58 ` Bin Liu
2015-09-14 17:08 ` Hans de Goede
2015-09-14 17:14 ` Bin Liu
2015-09-14 17:25 ` Hans de Goede
2015-09-14 17:53 ` Bin Liu
2015-09-14 17:56 ` Hans de Goede [this message]
2015-09-14 19:06 ` Bin Liu
2015-09-14 20:25 ` Maxime Ripard
2015-09-15 2:54 ` Hans de Goede
2015-09-15 4:20 ` Bin Liu
2016-05-04 10:25 ` Michal Suchanek
[not found] ` <706aa130-3ace-4059-a7c9-44147cd56c28@googlegroups.com>
[not found] ` <af013a0a-9257-4936-9e66-cb38f2e46369@googlegroups.com>
[not found] ` <0106707e-21f3-4aec-92ca-8b951af8a34e@googlegroups.com>
2017-05-12 9:16 ` Maxime Ripard
2015-09-26 12:50 ` Olliver Schinagl
[not found] ` <jwvmvw7zzg5.fsf-monnier+gmane.comp.hardware.netbook.arm.sunxi@gnu.org>
2015-09-28 7:04 ` [linux-sunxi] " Hans de Goede
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=55F70A67.3020502@redhat.com \
--to=hdegoede@redhat.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).