linux-kernel - Re: [PATCH v5 4/5] Extcon: support mutually exclusive relation between cables.

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: <CAJ0PZbTRRsyF4tGSYPagVmZQ495bmduYZ+FfPjn=Kp9hhcmhxQ@mail.gmail.com>
Date:	Wed, 22 Feb 2012 17:23:40 +0900
From:	MyungJoo Ham <myungjoo.ham@...sung.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, NeilBrown <neilb@...e.de>,
	Randy Dunlap <rdunlap@...otime.net>,
	Mike Lockwood <lockwood@...roid.com>,
	Arve Hjønnevag <arve@...roid.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Donggeun Kim <dg77.kim@...sung.com>, Greg KH <gregkh@...e.de>,
	Arnd Bergmann <arnd@...db.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Morten CHRISTIANSEN <morten.christiansen@...ricsson.com>,
	John Stultz <john.stultz@...aro.org>,
	Joerg Roedel <joerg.roedel@....com>
Subject: Re: [PATCH v5 4/5] Extcon: support mutually exclusive relation
 between cables.

On Mon, Feb 20, 2012 at 11:27 AM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Fri, Feb 10, 2012 at 03:40:37PM +0900, MyungJoo Ham wrote:
>
>> +What:                /sys/class/extcon/.../mutually_exclusive
>> +Date:                December 2011
>> +Contact:     MyungJoo Ham <myungjoo.ham@...sung.com>
>> +Description:
>> +             Shows the relations of mutually exclusiveness. For example,
>> +             if the mutually_exclusive array of extcon_dev is
>> +             {0x3, 0x5, 0xC, 0x0}, the, the output is:
>> +             # cat mutually_exclusive
>> +             0x3
>> +             0x5
>> +             0xC
>> +             #
>
> sysfs really isn't supposed to have more than one value per file so this
> should be something like a directory with one array element per file.
> It'd kind of be cheating but the values could be used as the filenames,
> though serial numbers would be more idiomatic.

Hmm.. I'll either use multiple files with a sub-directory or bin-attr
to inhabit the values. Or I'll search for any other convinient way to
express such an array thru sysfs.

Thanks.


Cheers!
MyungJoo.

-- 
MyungJoo Ham, Ph.D.
System S/W Lab,S/W Center, Samsung Electronics
--
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/