From: Pavel Machek <pavel@ucw.cz>
To: Vicentiu Galanopulo <vicentiu.galanopulo@remote-tech.co.uk>
Cc: lee@kernel.org, linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v3 2/2] leds: Add LED1202 I2C driverr
Date: Mon, 22 Jul 2024 09:06:23 +0200 [thread overview]
Message-ID: <Zp4E76JNHTyx21wE@duo.ucw.cz> (raw)
In-Reply-To: <ZpzkBM_ZwM8hdwgP@admins-MacBook-Air.local>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Hi!
> The LED1202 is a 12-channel low quiescent current LED driver.
> The output current can be adjusted separately for each channel by
> 8-bit analog (current sink input) and 12-bit digital (PWM) dimming control.
> The LED1202 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 (on 4096 steps).
> Analog dimming (on 256 steps) is per channel but common to all patterns.
> +static ssize_t st1202_duration_pattern_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct st1202_chip *chip;
> + struct dev_ext_attribute *eattr;
> + struct st1202_led_pattern_map *map;
New sysfs files need documentation.
Plus, this probably should use this interface, not custom one:
Documentation/ABI/testing/sysfs-class-led-trigger-pattern:What: /sys/class/leds/<led>/hw_pattern
It might be better to submit driver without pattern support, then
re-add it when driver is merged.
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2024-07-22 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 10:33 Vicentiu Galanopulo
2024-07-21 13:55 ` Markus Elfring
2024-07-22 7:03 ` Pavel Machek
2024-07-21 14:08 ` Christophe JAILLET
2024-07-22 7:06 ` Pavel Machek [this message]
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=Zp4E76JNHTyx21wE@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=vicentiu.galanopulo@remote-tech.co.uk \
/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
all inboxes | Powered by JetHome®