From: Marek Behun <kabel@blackhole.sk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Gabriel David <ultracoolguy4@protonmail.com>,
dmurphy@ti.com, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] leds: lm3697: Rename struct into more appropriate name
Date: Sat, 10 Oct 2020 23:50:45 +0200 [thread overview]
Message-ID: <20201010235045.4ba8cf51@blackhole.sk> (raw)
In-Reply-To: <20201010185700.GA8218@amd>
On Sat, 10 Oct 2020 20:57:00 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> On Fri 2020-10-09 15:51:35, Gabriel David wrote:
> > The mentioned struct, lm3697_led, was renamed to lm3697_bank since the
> > structure is representing the control banks. This name, in my opinion,
> > is more semantically correct. The pointers referring to it were also
> > renamed.
>
> > Signed-off-by: Gabriel David <ultracoolguy4@protonmail.com>
> > ---
> > Yes, this is the same Gabriel David from ultracoolguy@tutanota.org and
> > ultracoolguy@disroot.org. If you want me to confirm it I'll gladly do
> > it.
>
> No problem with that, and no need to resend. This can proably wait
> for 5.11...
>
> I'd like some comment from Dan... and perhaps I'd want to understand
> what the difference between LED and bank is.
>
> ...there can be more than one LED connected to the given bank, that's
> what you are pointing out?
>
> ...but these LEDs will always work in unison, and they are handled as
> single LED by Linux, right?
>
Pavel,
the controller can connect 3 LED strips (to 3 different pins on the
chip). There are 2 LED control banks (this is where you can set
brightness). For each LED strip (each output pin) you can configure to
which control bank it connects. So you have 3 LED strips and 2 control
banks, that is 2^3 = 8 different configurations of connecting LED
control bank to LED strip.
From the perspective of Linux you see the two control banks as 2 LED
class devices (because you are setting brightness for control banks,
not for the LED strips).
Marek
next prev parent reply other threads:[~2020-10-10 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 15:51 [PATCH v2] leds: lm3697: Rename struct into more appropriate name Gabriel David
2020-10-10 18:57 ` Pavel Machek
2020-10-10 21:50 ` Marek Behun [this message]
2020-10-12 14:27 ` Dan Murphy
2020-11-25 11:25 ` Pavel Machek
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=20201010235045.4ba8cf51@blackhole.sk \
--to=kabel@blackhole.sk \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=ultracoolguy4@protonmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.