devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alan Stern
	<stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>,
	Valentin Longchamp
	<valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: USB device nodes in device tree
Date: Sat, 04 Apr 2015 12:08:36 -0700	[thread overview]
Message-ID: <552036B4.9050405@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1503301534050.1407-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>

Le 30/03/2015 12:35, Alan Stern a écrit :
> On Mon, 30 Mar 2015, Valentin Longchamp wrote:
> 
>> Hello,
>>
>> We are currently developing a board with an USB MFD device (I2C and GPIOs are to
>> be supported). The device is soldered on the board and is the only one on the
>> bus, so the bus is not really "dynamic".
>>
>> Since it's an USB device, it should be dynamically detected by the kernel and it
>> would not require a node in the board's DTS. However, I need to have the devices
>> which are "behind" the MFD USB device to be in the DTS (I2C bus topology, and
>> some of the GPIOs are to be used directly by some other DTS nodes as well).
>>
>> Is there a way to add a node for USB device in a DTS ? Is there an available
>> example for this ?
> 
> No, there is no way to do it as far as I know.  The main problem is 
> that Device Tree is static whereas USB devices are dynamic.

The PCI(e) bus has the same problem, yet you can specify a PCI device
child node, and have a compatible string which will match the vendor
id/device id tuple, device class etc... such that you can use Device
Tree to add additional information not necessarily available in other
ways such as MAC addresses and similar.

Once the PCI bus is scanned, pci_device present in Device Tree get a
device_node pointer assigned.

I don't think there is anything doing this yet for USB devices, but
maybe that's something that should be there?
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-04-04 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 15:26 USB device nodes in device tree Valentin Longchamp
     [not found] ` <55196B2D.7000204-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2015-03-30 19:35   ` Alan Stern
     [not found]     ` <Pine.LNX.4.44L0.1503301534050.1407-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2015-04-04 19:08       ` Florian Fainelli [this message]
     [not found]         ` <552036B4.9050405-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-04-04 23:48           ` Arnd Bergmann

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=552036B4.9050405@gmail.com \
    --to=f.fainelli-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org \
    --cc=valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@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).