On Wed, 9 Jan 2019 at 15:55, Auger Eric <eric.auger@xxxxxxxxxx> wrote:
>
> Hi Geert,
>
> On 1/3/19 10:42 AM, Geert Uytterhoeven wrote:
> > Add a fallback for instantiating generic devices without a type-specific
> > or compatible-specific instantiation method. This will be used when no
> > other match is found.
> >
> > Generic device instantiation avoids having to write device-specific
> > instantiation methods for each and every "simple" device using only a
> > set of generic properties. Devices that need more specialized handling
> > can still provide their own instantiation methods.
> > + /* Ignoring the following may or may not work, hence the warning */
> > + { "gpio-ranges", PROP_WARN }, /* no support for pinctrl yet */
> > + { "dmas", PROP_WARN }, /* no support for external DMACs yet */
> I would be tempted to simply reject things that may not work.
More generally, this whole feature seems to be "allow things that
might not work", isn't it? Otherwise we could just have explicit
whitelists for the devices we want to allow passthrough of and
that we've tested to work.
I have to say I'm not really very enthusiastic about
enhancing this to allow random device passthrough,
because it encourages further use of this. If people
want hardware that can be passed through they should
put it behind a bus that can be probed and can go
behind an IOMMU, ie pci or some equivalent. That
is a supportable hardware mechanism. All this
machinery feels very heath-robinson...
thanks
-- PMM
