[i2c] [patch/rfc 2.6.26-rc5] i2c: schedule legacy gpio driver removal

David Brownell david-b at pacbell.net
Thu Jun 12 22:55:23 CEST 2008

On Thursday 12 June 2008, Jean Delvare wrote:
> > I think the only other blocking issue would be a way to configure
> > such new-style drivers from sysfs, primarily for one-off hardware
> > hacking usage (in at least this case).
> This is the problem. Until there is a way to instantiate new-style
> drivers from user-space, we just can't remove the deprecated drivers.
> Even tagging it as deprecated is dishonest to some extent.

Not really; anyone who *can* use the newer stuff should do so.
If they can't, the older stuff is still there.

> So I see no 
> point in adding these drivers to the feature removal list for now. We
> can do that later, when we really offer an alternative with the same
> features.
> You shouldn't fear that we forget to remove these drivers. They are the
> dust in my eye, I can't forget them.

OK.  :)

> >                                       Teaching the two new-style
> > drivers to use dynamic GPIO number allocation when there's no
> > platform_data is trivial,
> Good to know...
> >                           and not otherwise desirable.
> I'm confused now.

The GPIOs can't really be used in-kernel without platform data.

More information about the i2c mailing list