> >> probing and does not have an .of_match_table defined in it's
> >> driver struct? I mean, what could possibly match that
> >> compatible string? The .name field will take care of naming
> >> the device does it not?
> >
> > You only need that stuff if you require _extra_ bindings. Things like
>
On Tue, May 14, 2013 at 11:26 AM, Lee Jones wrote:
>> probing and does not have an .of_match_table defined in it's
>> driver struct? I mean, what could possibly match that
>> compatible string? The .name field will take care of naming
>> the device does it not?
>
> You only need that stuff if you
On Tue, 14 May 2013, Linus Walleij wrote:
> On Wed, May 8, 2013 at 3:29 PM, Lee Jones wrote:
>
> > When booting with Device Tree enabled the MFD core uses each device's
> > compatible string to find and allocate its associated of_node pointer,
> > which in turn is passed to the driver via the pl
On Wed, May 8, 2013 at 3:29 PM, Lee Jones wrote:
> When booting with Device Tree enabled the MFD core uses each device's
> compatible string to find and allocate its associated of_node pointer,
> which in turn is passed to the driver via the platform_device struct.
> Without it, the driver won't
4 matches
Mail list logo
