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
| ||
|
Date: Thu, 10 Dec 2009 20:13:58 -0800 From: David Brownell <david-b@...bell.net> To: Greg KH <gregkh@...e.de> Cc: Jani Nikula <ext-jani.1.nikula@...ia.com>, dbrownell@...rs.sourceforge.net, linux-kernel@...r.kernel.org, dsilvers@...tec.co.uk, ben@...tec.co.uk, Artem.Bityutskiy@...ia.com, akpm@...ux-foundation.org Subject: Re: [PATCH 3/3] gpiolib: use chip->names for symlinks, always use gpioN for device names On Thursday 10 December 2009, Greg KH wrote: > > > IMO a "good" solution in this space needs to accept that > > those names are not going to be globally unique ... but > > that they'll be unique within some context, of necessity. > > > > If Greg doesn't want to see those names under classes, > > so be it ... but where should they then appear? > > As a sysfs file within the device directory called 'name'? Then just > grep through the tree to find the right device, that also handles > duplicates just fine, right? I want a concrete example. Those chip->names things don't seem helpful to me though... If for example I were building a JTAG adapter on Linux, it might consist of a spidev node (chardev) plus a handful of GPIOs. So "the device directory" would be the sysfs home of that spidev node (or some variant)? And inside that directory would be files named after various signals that are used as GPIOs ... maybe SRST, TRST, and DETECT to start with? Holding some cookie that gets mapped to those GPIO's sysfs entries? I confess I'd still think a symlink from that directory to the real GPIO would be easier to work with... - Dave -- 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