From: Vicentiu Galanopulo <vicentiu.galanopulo@remote-tech.co.uk>
To: rdunlap@infradead.org, pavel@ucw.cz, lee@kernel.org,
corbet@lwn.net, linux-leds@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/3] Documentation:leds: Add leds-st1202.rst
Date: Wed, 30 Oct 2024 23:09:25 +0100 [thread overview]
Message-ID: <ZyKulcUCW3kk1AYX@admins-Air> (raw)
In-Reply-To: <0ae13ad4-342a-48ca-bd7a-8f15f6d99504@infradead.org>
Hi Randy,
Thanks for the review. Addressed all comments.
Signed-off-by: Vicentiu Galanopulo <vicentiu.galanopulo@remote-tech.co.uk>
---
Changes in v2: Implement review comments
Documentation/leds/leds-st1202.rst | 36 ++++++++++++++++++++++++++++++
1 file changed, 36 insertions(+)
create mode 100644 Documentation/leds/leds-st1202.rst
diff --git a/Documentation/leds/leds-st1202.rst b/Documentation/leds/leds-st1202.rst
new file mode 100644
index 000000000000..72286a512c69
--- /dev/null
+++ b/Documentation/leds/leds-st1202.rst
@@ -0,0 +1,36 @@
+.. SPDX-License-Identifier: GPL-2.0
+
+============================================
+Kernel driver for STMicroelectronics LED1202
+============================================
+
+/sys/class/leds/<led>/hw_pattern
+--------------------------------
+
+Specify a hardware pattern for the ST1202 LED. The LED
+controller implements 12 low-side current generators
+with independent dimming control. Internal volatile memory
+allows the user to store up to 8 different patterns.
+Each pattern is a particular output configuration in terms
+of PWM duty-cycle and duration (ms).
+
+To be compatible with the hardware pattern
+format, maximum 8 tuples of brightness (PWM) and duration must
+be written to hw_pattern.
+
+- Min pattern duration: 22 ms
+- Max pattern duration: 5660 ms
+
+The format of the hardware pattern values should be:
+"brightness duration brightness duration ..."
+
+/sys/class/leds/<led>/repeat
+----------------------------
+
+Specify a pattern repeat number, which is common for all channels.
+Default is 1; negative numbers and 0 are invalid.
+
+This file will always return the originally written repeat number.
+
+When the 255 value is written to it, all patterns will repeat
+indefinitely.
--
2.39.3 (Apple Git-145)
next prev parent reply other threads:[~2024-10-30 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 14:48 [PATCH v1 3/3] Documentation:leds: Add leds-st1202.rst Vicentiu Galanopulo
2024-10-26 17:17 ` Randy Dunlap
2024-10-30 22:09 ` Vicentiu Galanopulo [this message]
2024-10-30 22:15 ` Randy Dunlap
2024-11-04 19:32 ` Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZyKulcUCW3kk1AYX@admins-Air \
--to=vicentiu.galanopulo@remote-tech.co.uk \
--cc=corbet@lwn.net \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox