From: Lee Jones <lee@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Vicentiu Galanopulo <vicentiu.galanopulo@remote-tech.co.uk>
Subject: Re: (subset) [PATCH v11 3/3] leds: Add LED1202 I2C driver
Date: Tue, 11 Feb 2025 10:15:22 +0000 [thread overview]
Message-ID: <20250211101522.GL1868108@google.com> (raw)
In-Reply-To: <CAMuHMdXtDd-KSeX_8nhj_J0X33WRT47_v3m01qdBN01-p4xVjA@mail.gmail.com>
On Tue, 11 Feb 2025, Geert Uytterhoeven wrote:
> Hi Lee,
>
> On Mon, 10 Feb 2025 at 18:01, Lee Jones <lee@kernel.org> wrote:
> > On Mon, 10 Feb 2025, Lee Jones wrote:
> > > On Tue, 21 Jan 2025, Geert Uytterhoeven wrote:
> > >
> > > > Hi Lee,
> > > >
> > > > On Thu, Jan 9, 2025 at 11:31 AM Lee Jones <lee@kernel.org> wrote:
> > > > > On Wed, 18 Dec 2024 18:33:59 +0000, Vicentiu Galanopulo wrote:
> > > > > > 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. Each device tree LED node will have a corresponding
> > > > > > entry in /sys/class/leds with the label name. The brightness property
> > > > > > corresponds to the per channel analog dimming, while the patterns[1-8] to the
> > > > > > PWM dimming control.
> > > > > >
> > > > > > [...]
> > > > >
> > > > > Applied, thanks!
> > > > >
> > > > > [3/3] leds: Add LED1202 I2C driver
> > > > > commit: 939757aafeb9c266dda37657ee5f7a73ffd35ae2
> > > >
> > > > You also have commit 259230378c65ebb6 ("leds: Add LED1202 I2C driver")
> > > > in mfd/for-mfd-next, which dropped the change to drivers/leds/Makefile,
> > > > and changed the Link:-tag to point to the older version v10?
> > >
> > > Interesting. Not sure I noticed and if I did, I must have fixed it.
> > >
> > > This is the commit that made it in:
> > >
> > > 939757aafeb9 ("leds: Add LED1202 I2C driver")
> >
> > Scratch that - looks like:
> >
> > 259230378c65 ("leds: Add LED1202 I2C driver")
> >
> > ... also made it in. However the Makefile line survived:
> >
> > drivers/leds/Makefile:obj-$(CONFIG_LEDS_ST1202) += leds-st1202.o
> >
> > Did anything break or is all as expected?
>
> The end result is fine. History might confuse people (the (un)happy
> few who care about history ;-), as "git log -p v6.14-rc1 --
> drivers/leds/Makefile" shows 939757aafeb9, while "git log -p v6.14-rc1
> -- drivers/leds/leds-st1202.c" shows 259230378c65, linking to the
> older version.
Sorry about that. I am one who cares a great deal about history.
One of the pitfalls of maintaining multiple repos I guess.
#humanafterall :)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-02-11 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 18:33 [PATCH v11 0/3] Add LED1202 LED Controller Vicentiu Galanopulo
2024-12-18 18:33 ` [PATCH v11 1/3] Documentation:leds: Add leds-st1202.rst Vicentiu Galanopulo
2024-12-18 18:33 ` [PATCH v11 2/3] dt-bindings: leds: Add LED1202 LED Controller Vicentiu Galanopulo
2024-12-18 18:33 ` [PATCH v11 3/3] leds: Add LED1202 I2C driver Vicentiu Galanopulo
2025-01-09 10:30 ` (subset) " Lee Jones
2025-01-21 11:56 ` Geert Uytterhoeven
2025-02-10 16:59 ` Lee Jones
2025-02-10 17:01 ` Lee Jones
2025-02-11 8:02 ` Geert Uytterhoeven
2025-02-11 10:15 ` Lee Jones [this message]
2025-01-09 10:30 ` [PATCH v11 0/3] Add LED1202 LED Controller Lee Jones
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=20250211101522.GL1868108@google.com \
--to=lee@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@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=robh@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;
as well as URLs for NNTP newsgroup(s).