linux-kernel - Re: [PATCH] gpiolib: use platform GPIO mappings as fallback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <52985FC8.70008@nvidia.com>
Date:	Fri, 29 Nov 2013 18:35:04 +0900
From:	Alex Courbot <acourbot@...dia.com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpiolib: use platform GPIO mappings as fallback

On 11/29/2013 06:29 PM, Linus Walleij wrote:
> On Sat, Nov 23, 2013 at 11:34 AM, Alexandre Courbot <acourbot@...dia.com> wrote:
>
>> For platforms that use device tree or ACPI as the standard way to look
>> GPIOs up, allow the platform-defined GPIO mappings to be used as a
>> fallback. This may be useful for platforms that need extra GPIOs mappings
>> not defined by the firmware.
>>
>> Signed-off-by: Alexandre Courbot <acourbot@...dia.com>
>
> Applied for fixes. I was considering applying it for the next
> kernel but it depends on the former patches and we should
> expect a bit of extra fuzz now with the new API.

Thanks - I'd rather have all the problems coming in a row than 
incrementally as we introduce potentially incompatible changes.

Alex.

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