linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: FUKAUMI Naoki <naoki@radxa.com>
Cc: linux-leds@vger.kernel.org, pavel@ucw.cz
Subject: Re: [PATCH] leds: pwm-multicolor: fix multicolor PWM LED lights up without any setting
Date: Thu, 22 Aug 2024 09:24:52 +0100	[thread overview]
Message-ID: <20240822082452.GE6858@google.com> (raw)
In-Reply-To: <7DDC06B563854ED8+65e7204f-76df-4f36-8544-bede36a519fd@radxa.com>

On Thu, 22 Aug 2024, FUKAUMI Naoki wrote:

> Hi,
> 
> On 8/22/24 06:26, FUKAUMI Naoki wrote:
> > Hi,
> > 
> > On 8/22/24 01:11, Lee Jones wrote:
> > > On Fri, 16 Aug 2024, FUKAUMI Naoki wrote:
> > > 
> > > > from drivers/leds/leds-pwm.c:led_pwm_set(),
> > > > 
> > > > /*
> > > >   * Disabling a PWM doesn't guarantee that it emits the inactive level.
> > > >   * So keep it on. Only for suspending the PWM should be
> > > > disabled because
> > > >   * otherwise it refuses to suspend. The possible downside is that the
> > > >   * LED might stay (or even go) on.
> > > >   */
> > > > 
> > > > do the same in led_pwm_mc_set().
> > > > 
> > > > this fixes LEDs light up without any setting (i.e. brightness is 0) on
> > > > Radxa E25.
> > > 
> > > Please redraft the commit message into proper sentences, complete with
> > > correct grammar.  All sentences should start with an uppercase char.
> > 
> > Thank you for your review!
> > 
> > I'll do it in next ver.
> > 
> > > Copying comment-blocks into commit messages to save authors from writing
> > > one isn't really the done thing.
> > 
> > Sorry, I could not understand this part. What should I do for this?
> 
> I (probably) understand what you said. I need to explain detail in my own
> words and use correct English.
> 
> unfortunately my knowledge about electrical circuits and English is not
> sufficient for now.
> I need some time to learn some things for writing "why my fix is correct".
> 
> then, I will not be able to send v2 so soon. if someone who understand well
> about this problem and the fix, feel free to reuse my patch (or make better
> patch).

You understood enough to read the comment and realise that it was
related.  Simply reword the comment block that you copied and pasted to
explain why this is also relevant to your device.

This is the sort of thing that AI might be able to help you with.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2024-08-22  8:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 10:26 [PATCH] leds: pwm-multicolor: fix multicolor PWM LED lights up without any setting FUKAUMI Naoki
2024-08-21 16:11 ` Lee Jones
2024-08-21 21:26   ` FUKAUMI Naoki
2024-08-22  7:22     ` FUKAUMI Naoki
2024-08-22  8:24       ` Lee Jones [this message]
2024-12-10  7:36       ` FUKAUMI Naoki
2024-12-12 19:04         ` Lee Jones
2024-12-12 21:19           ` FUKAUMI Naoki
2024-12-13 16:35             ` Lee Jones
2024-12-13 21:11               ` FUKAUMI Naoki
2024-12-16  9:51                 ` 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=20240822082452.GE6858@google.com \
    --to=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=naoki@radxa.com \
    --cc=pavel@ucw.cz \
    /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).