Re: [patch/rfc 2.6.19-rc5] arch-neutral GPIO calls

David Brownell wrote:

I suspect that userspace GPIO accessors should only be written once
though, and they're going to be in the "don't care" category. So
lack of such a "message compatible" GPIO call set might reasonably
hold up merging that sort of (configfs?) interface.


Yes, the userspace interface is by far the biggest issue here.

-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [PATCH v2] Add bt8xxgpio driver
    ... The purpose of the bt8xxgpio driver is to export all of the 24 GPIO pins ... nor in any GPIO source file. ... David Brownell. ... you might want to raise a MAINTAINERS patch. ...
    (Linux-Kernel)
  • Re: [Bulk] Re: [patch/rfc 2.6.19-rc5] arch-neutral GPIO calls
    ... David Brownell wrote: ... I think the GPIO management stuff can do it properly on my behalf, given the information we have to acquire to get the GPIO API to work in the first place. ... Bill Gatliff ...
    (Linux-Kernel)
  • Re: [patch/rfc 2.6.19-rc5] arch-neutral GPIO calls
    ... David Brownell wrote: ... they could easily have dedicated pins!! ... that there's even a one-to-one association between pins and GPIOs ... ... refcounting nor GPIO claiming can be sufficient to prevent such problems ... ...
    (Linux-Kernel)