[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130812144110.GA6427@sirena.org.uk>
Date: Mon, 12 Aug 2013 15:41:10 +0100
From: Mark Brown <broonie@...nel.org>
To: Grant Likely <grant.likely@...aro.org>
Cc: Rob Herring <rob.herring@...xeda.com>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Stephen Warren <swarren@...dotorg.org>,
Ian Campbell <ian.campbell@...rix.com>,
Felipe Balbi <balbi@...com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devicetree@...nel.org, Linux USB list <linux-usb@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Non-enumerable devices on USB and other enumerable buses
On Sun, Aug 11, 2013 at 11:08:37PM +0100, Grant Likely wrote:
> full enumerating like that with either ACPI or FDT, but we could allow
> for sparse population of devices when something is fixed like a
> soldered down USB hub or USB Ethernet MAC.
I agree, there's no point in listing things that can be done
automatically - it's just introducing potential for error.
> To make it work would probably require a hook in the USB enumeration
> path to look for matching nodes in DT/ACPI and attach it to the struct
> device.
Yes, that was where I was heading too. Have a mechanism for matching up
hotplugged devices with pre-registered ones which appear from firmware
or wherever if their IDs match. It'd need some mechanism for drivers to
opt into being bound to devices that aren't physically there I think so
that normal drivers for enumerated devices don't get confused.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists