linux-kernel - Re: [PATCH 09/10] Documentation: leds-lp5521,lp5523: update device attribute information

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]

Date:	Tue, 13 Aug 2013 14:00:04 -0700
From:	Bryan Wu <cooloney@...il.com>
To:	Milo Kim <woogyom.kim@...il.com>
Cc:	Pali Rohár <pali.rohar@...il.com>,
	Linux LED Subsystem <linux-leds@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>, Milo Kim <milo.kim@...com>
Subject: Re: [PATCH 09/10] Documentation: leds-lp5521,lp5523: update device
 attribute information

On Thu, Aug 8, 2013 at 12:59 AM, Milo Kim <woogyom.kim@...il.com> wrote:
> Now, all legacy application interfaces are restored.
> Each driver documentation is updated.
>

Good to merge, thanks,
-Bryan

> Cc: Pali Rohár <pali.rohar@...il.com>
> Signed-off-by: Milo Kim <milo.kim@...com>
> ---
>  Documentation/leds/leds-lp5521.txt |   20 +++++++++++++++++++-
>  Documentation/leds/leds-lp5523.txt |   21 ++++++++++++++++++++-
>  2 files changed, 39 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/leds/leds-lp5521.txt b/Documentation/leds/leds-lp5521.txt
> index 79e4c2e..d08d8c1 100644
> --- a/Documentation/leds/leds-lp5521.txt
> +++ b/Documentation/leds/leds-lp5521.txt
> @@ -18,7 +18,25 @@ All three channels can be also controlled using the engine micro programs.
>  More details of the instructions can be found from the public data sheet.
>
>  LP5521 has the internal program memory for running various LED patterns.
> -For the details, please refer to 'firmware' section in leds-lp55xx.txt
> +There are two ways to run LED patterns.
> +
> +1) Legacy interface - enginex_mode and enginex_load
> +  Control interface for the engines:
> +  x is 1 .. 3
> +  enginex_mode : disabled, load, run
> +  enginex_load : store program (visible only in engine load mode)
> +
> +  Example (start to blink the channel 2 led):
> +  cd   /sys/class/leds/lp5521:channel2/device
> +  echo "load" > engine3_mode
> +  echo "037f4d0003ff6000" > engine3_load
> +  echo "run" > engine3_mode
> +
> +  To stop the engine:
> +  echo "disabled" > engine3_mode
> +
> +2) Firmware interface - LP55xx common interface
> +  For the details, please refer to 'firmware' section in leds-lp55xx.txt
>
>  sysfs contains a selftest entry.
>  The test communicates with the chip and checks that
> diff --git a/Documentation/leds/leds-lp5523.txt b/Documentation/leds/leds-lp5523.txt
> index 899fdad..5b3e91d 100644
> --- a/Documentation/leds/leds-lp5523.txt
> +++ b/Documentation/leds/leds-lp5523.txt
> @@ -28,7 +28,26 @@ If both fields are NULL, 'lp5523' is used by default.
>  /sys/class/leds/lp5523:channelN  (N: 0 ~ 8)
>
>  LP5523 has the internal program memory for running various LED patterns.
> -For the details, please refer to 'firmware' section in leds-lp55xx.txt
> +There are two ways to run LED patterns.
> +
> +1) Legacy interface - enginex_mode, enginex_load and enginex_leds
> +  Control interface for the engines:
> +  x is 1 .. 3
> +  enginex_mode : disabled, load, run
> +  enginex_load : microcode load (visible only in load mode)
> +  enginex_leds : led mux control (visible only in load mode)
> +
> +  cd /sys/class/leds/lp5523:channel2/device
> +  echo "load" > engine3_mode
> +  echo "9d80400004ff05ff437f0000" > engine3_load
> +  echo "111111111" > engine3_leds
> +  echo "run" > engine3_mode
> +
> +  To stop the engine:
> +  echo "disabled" > engine3_mode
> +
> +2) Firmware interface - LP55xx common interface
> +  For the details, please refer to 'firmware' section in leds-lp55xx.txt
>
>  Selftest uses always the current from the platform data.
>
> --
> 1.7.9.5
>
--
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/