On Thu, Jan 22, 2015 at 6:44 AM, Olliver Schinagl wrote:
> Hey Alexandre,
>
> On 01/19/2015 05:04 AM, Alexandre Courbot wrote:
>>
>> On Wed, Jan 7, 2015 at 6:08 PM, Olliver Schinagl
>> wrote:
>>>
>>> From: Olliver Schinagl
>>>
>>> The gpio binding document says that new code should always use na
Hey Alexandre,
On 01/19/2015 05:04 AM, Alexandre Courbot wrote:
On Wed, Jan 7, 2015 at 6:08 PM, Olliver Schinagl
wrote:
From: Olliver Schinagl
The gpio binding document says that new code should always use named
gpios. Patch 40b73183 added support to parse a list of gpios from child
nodes, b
On Wed, Jan 7, 2015 at 6:08 PM, Olliver Schinagl
wrote:
> From: Olliver Schinagl
>
> The gpio binding document says that new code should always use named
> gpios. Patch 40b73183 added support to parse a list of gpios from child
> nodes, but does not make it possible to use named gpios. This patch
On Wed, Jan 7, 2015 at 10:08 AM, Olliver Schinagl
wrote:
> From: Olliver Schinagl
>
> The gpio binding document says that new code should always use named
> gpios. Patch 40b73183 added support to parse a list of gpios from child
> nodes, but does not make it possible to use named gpios. This pat
On Wed, Jan 07, 2015 at 10:08:40AM +0100, Olliver Schinagl wrote:
> From: Olliver Schinagl
>
> The gpio binding document says that new code should always use named
> gpios. Patch 40b73183 added support to parse a list of gpios from child
> nodes, but does not make it possible to use named gpios.
From: Olliver Schinagl
The gpio binding document says that new code should always use named
gpios. Patch 40b73183 added support to parse a list of gpios from child
nodes, but does not make it possible to use named gpios. This patch adds
the con_id property and implements it is done in gpiolib.c,
6 matches
Mail list logo