| 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
| ||
|
Message-ID: <CACRpkdZ8AO5SrjJvJxvpauEadQOKMNaW_Pxxzhjk5hWnVB1b+g@mail.gmail.com> Date: Mon, 6 Aug 2012 08:35:51 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Stephen Warren <swarren@...dotorg.org> Cc: Johannes Stezenbach <js@...21.net>, devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org Subject: Re: DT GPIO numbering? On Mon, Aug 6, 2012 at 4:18 AM, Stephen Warren <swarren@...dotorg.org> wrote: > I can't comment on the sysfs-vs-dev interface location, but I don't > think it addresses Johannes' issue; finding out which GPIO IDs are > provided by which devices. > > Perhaps in each device's sysfs node, there should be some information > re: which GPIO range it provides. Right now, perhaps a text file with > the GPIO base it it. Yes that could work ... > With the new /dev interface you mention above, > perhaps a symlink to the /dev file, or a file containing the /dev file's > major/minor number. Or, is there such a thing already (other than > debugfs's gpio file). Nothing I know of, but yes the day we come up with something, it needs to be backward-compatible some way. The problem is that there is really no reference userspace like "lsgpio" or so. Maybe the first step could be to create that. Yours, Linus Walleij -- 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/
Powered by blists - more mailing lists