On Tue, Jul 8, 2014 at 5:21 PM, Linus Walleij wrote:
> On Tue, Jul 1, 2014 at 7:45 AM, Alexandre Courbot wrote:
>
>> sysfs support is currently entangled within the core GPIO support, while
>> it should relly just be a (privileged) user of the integer GPIO API.
>> This patch is a first step
On Tue, Jul 1, 2014 at 7:45 AM, Alexandre Courbot wrote:
> sysfs support is currently entangled within the core GPIO support, while
> it should relly just be a (privileged) user of the integer GPIO API.
> This patch is a first step towards making the gpiolib code more readable
> by splitting it
On Tue, Jul 1, 2014 at 7:45 AM, Alexandre Courbot acour...@nvidia.com wrote:
sysfs support is currently entangled within the core GPIO support, while
it should relly just be a (privileged) user of the integer GPIO API.
This patch is a first step towards making the gpiolib code more readable
On Tue, Jul 8, 2014 at 5:21 PM, Linus Walleij linus.wall...@linaro.org wrote:
On Tue, Jul 1, 2014 at 7:45 AM, Alexandre Courbot acour...@nvidia.com wrote:
sysfs support is currently entangled within the core GPIO support, while
it should relly just be a (privileged) user of the integer GPIO
sysfs support is currently entangled within the core GPIO support, while
it should relly just be a (privileged) user of the integer GPIO API.
This patch is a first step towards making the gpiolib code more readable
by splitting it into logical parts.
Move all sysfs support to their own source
sysfs support is currently entangled within the core GPIO support, while
it should relly just be a (privileged) user of the integer GPIO API.
This patch is a first step towards making the gpiolib code more readable
by splitting it into logical parts.
Move all sysfs support to their own source
6 matches
Mail list logo
