linux-kernel - Re: [PATCH v2] pinctrl: bcm2835: Start GPIO numeration at zero

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <544ECFB4.7040704@linux.com>
Date:	Tue, 28 Oct 2014 00:05:24 +0100
From:	Matthias Klein <matthias.klein@...ux.com>
To:	Stephen Warren <swarren@...dotorg.org>,
	linux-rpi-kernel@...ts.infradead.org, linus.walleij@...aro.org
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] pinctrl: bcm2835: Start GPIO numeration at zero


Am 27.10.2014 um 23:44 schrieb Stephen Warren:
> On 10/27/2014 04:09 PM, Matthias Klein wrote:
>> Numerate the GPIOs from 0..53 instead of 202..255.
>
> What's the motivation for this? The GPIO IDs should all come from DT, 
> which encodes everything as an ID relative to a particular 
> controllers, and hence the actual value of the base address should be 
> irrelevant.
- To be in sync with the GPIO numbers in the datasheet / documentation
- For userland applications which rely on these GPIO numbers

--
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/