From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Ian Molton <ian.molton-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: DT and probeable devices...
Date: Tue, 4 Dec 2012 14:05:33 +0000 [thread overview]
Message-ID: <CACxGe6vDNu04HtHVLBS6fJ5GDVfGb1dD7fq-HPh+vmcc+FWxcQ@mail.gmail.com> (raw)
In-Reply-To: <50BDF6B5.7070306-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
On Tue, Dec 4, 2012 at 1:12 PM, Ian Molton <ian.molton-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org> wrote:
> Hi,
>
> Im working on the OMAP5 pandaboard, and have run across a corner case.
>
> the Ethernet is USB attached (and thus discovered / probed by the USB
> controller).
>
> However it has a reset line thats a GPIO on the board.
>
> Is DT supposed to be able to cover cases like this? If so, how?
USB devices can be described as child nodes of the USB bus, though
they typically aren't because as you mention the USB bus is
discoverable. There is a binding for USB devices[1]. I don't believe
the kernel currently does anything to match USB dt nodes with a
usb_device, but it wouldn't be hard to hook up. You'd probably need a
hook in usb_new_device() to attach the of_node to the usb_device if it
exists. Then the driver would have the ability to query the DT node
for things like gpios.
[1] http://www.openfirmware.org/1275/bindings/usb/usb-1_0.ps
g.
next prev parent reply other threads:[~2012-12-04 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 13:12 DT and probeable devices Ian Molton
[not found] ` <50BDF6B5.7070306-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2012-12-04 14:05 ` Grant Likely [this message]
[not found] ` <CACxGe6vDNu04HtHVLBS6fJ5GDVfGb1dD7fq-HPh+vmcc+FWxcQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-04 23:04 ` David Gibson
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=CACxGe6vDNu04HtHVLBS6fJ5GDVfGb1dD7fq-HPh+vmcc+FWxcQ@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=ian.molton-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.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).