[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d7a44b77-a8e5-d4fa-9a11-96cdde862b4c@lechnology.com>
Date: Tue, 9 Apr 2019 08:12:57 -0500
From: David Lechner <david@...hnology.com>
To: Pavel Machek <pavel@....cz>,
William Breathitt Gray <vilhelm.gray@...il.com>
Cc: gregkh@...uxfoundation.org, jic23@...nel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
fabrice.gasnier@...com, benjamin.gaignard@...com, knaack.h@....de,
lars@...afoo.de, pmeerw@...erw.net, akpm@...ux-foundation.org,
robh+dt@...nel.org, mark.rutland@....com, shawnguo@...nel.org,
leoyang.li@....com, daniel.lezcano@...aro.org, tglx@...utronix.de,
thierry.reding@...il.com, esben@...bendal.dk,
linux-pwm@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
patrick.havelange@...ensium.com,
Jonathan Cameron <Jonathan.Cameron@...wei.com>
Subject: Re: [PATCH v10 02/18] counter: Documentation: Add Generic Counter
sysfs documentation
On 4/8/19 4:55 PM, Pavel Machek wrote:
>
> pavel@amd:~$ cat /sys/power/state
> freeze mem disk
>
> And we use [] to mark current selection:
I know this is used elsewhere, but I don't think it is a good pattern
to copy. Parsing it from user-space is annoying. Also it breaks the
sysfs rule of "one item per file" since it tells us two things - the
list of possible values _and_ the current active value.
>
> pavel@amd:~$ cat /sys/class/leds/tpacpi\:\:thinkvantage/trigger
> [none] bluetooth-power rfkill-any rfkill-none kbd-scrolllock
> kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock
> kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock
> kbd-ctrlrlock AC-online BAT0-charging-or-full BAT0-charging BAT0-full
> BAT0-charging-blink-full-solid rfkill0 phy0rx phy0tx phy0assoc
> phy0radio phy0tpt mmc0 timer heartbeat audio-mute audio-micmute
> rfkill1
>
> Note this only works if you have less than PAGE_SIZE of entries... and
> will never have more.
>
> Pavel
>
Powered by blists - more mailing lists