Hi,
On Fri, May 6, 2011 at 2:47 AM, Hans J. Koch <[email protected]> wrote:
> On Thu, May 05, 2011 at 08:40:44AM +0200, Michal Simek wrote:
>
> I think we've got it.
>
> Thanks,
> Hans
>
> > Adding OF binding to genirq.
> > Version string is setup to the "devicetree".
> >
> > Compatible string is not setup for now but you can add your
> > custom compatible string to uio_of_genirq_match structure.
> >
> > For example with "vendor,device" compatible string:
> > static const struct of_device_id __devinitconst uio_of_genirq_match[] = {
> > { .compatible = "vendor,device", },
> > { /* empty for now */ },
> > };
> >
> > Signed-off-by: Michal Simek <[email protected]>
>
> Signed-off-by: Hans J. Koch <[email protected]>
>
> > CC: Hans J. Koch <[email protected]>
> > CC: Arnd Bergmann <[email protected]>
> > CC: John Williams <[email protected]>
> > CC: Grant Likely <[email protected]>
> > CC: Wolfram Sang <[email protected]>
>
Sorry for adding to this discussion so late...
I fail to see how a device described in the device tree can be bound to this
generic driver, as the match table is empty. I read in the description:
> Compatible string is not setup for now but you can add your
> custom compatible string to uio_of_genirq_match structure.
>
> For example with "vendor,device" compatible string:
> static const struct of_device_id __devinitconst uio_of_genirq_match[] = {
> { .compatible = "vendor,device", },
> { /* empty for now */ },
> };
So, this would mean that for a given project, you need to modify the sources
of the *generic* driver ?
Thanks for clarifying,
Thomas
_______________________________________________
devicetree-discuss mailing list
[email protected]
https://lists.ozlabs.org/listinfo/devicetree-discuss
