From: Conor Dooley <conor@kernel.org>
To: Nylon Chen <nylon.chen@sifive.com>
Cc: "Jessica Clarke" <jrtc27@jrtc27.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
nylon7717@gmail.com, zong.li@sifive.com, greentime.hu@sifive.com,
vincent.chen@sifive.com,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH 0/2] Change PWM-controlled LED pin active mode and algorithm
Date: Wed, 18 Jan 2023 08:13:49 +0000 [thread overview]
Message-ID: <Y8eqPdifnWbMQI/T@spud> (raw)
In-Reply-To: <CAHh=Yk9jUFiwzw+RQDoyb7xDoHGXFzNprdXn8szmMZb5FB4jLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2726 bytes --]
Hey Nylon,
On Wed, Jan 18, 2023 at 10:32:25AM +0800, Nylon Chen wrote:
> Conor Dooley <conor@kernel.org> 於 2023年1月14日 週六 下午10:00寫道:
> > On Fri, Jan 13, 2023 at 07:24:56PM +0000, Jessica Clarke wrote:
> > > On 13 Jan 2023, at 18:32, Conor Dooley <conor@kernel.org> wrote:
> > > > Please delete link 2, convert the other two to standard Link: tags and
> > > > put this information in the dts patch. Possibly into the PWM patch too,
> > > > depending on what the PWM maintainers think.
> > > > This info should be in the commit history IMO and the commit message for
> > > > the dts patch says what's obvious from the diff without any explanation
> > > > as to why.
> > > >
> > > > I did a bit of looking around on lore, to see if I could figure out
> > > > why it was done like this in the first place, and I found:
> > > > https://lore.kernel.org/linux-pwm/CAJ2_jOG2M03aLBgUOgGjWH9CUxq2aTG97eSX70=UaSbGCMMF_g@mail.gmail.com/
> > >
> > > That DTS documentation makes no sense to me, why does what the LED is
> > > wired to matter?
> >
> > ```
> > active-low:
> > description:
> > For PWMs where the LED is wired to supply rather than ground.
> > ```
> >
> > > Whether you have your transistor next to ground or
> > > next to Vdd doesn’t matter, what matters is whether the transistor is
> > > on or off. Maybe what they mean is whether the *PWM's output* / *the
> > > transistor's input* is pulled to ground or Vdd? In which case the
> > > property would indeed not apply here.
> > >
> > > Unless that’s written assuming the LED is wired directly to the PWM, in
> > > which case it would make sense, but that’s a very narrow-minded view of
> > > what the PWM output is (directly) driving.
> >
> > I would suspect that it was written with that assumption.
> > Probably was the case on the specific board this property was originally
> > added for.
> As you can see, there is also the same description in U-Boot.
>
> But in U-Boot, the DTS of Unmatched/Unleashed has not been added active-low.
>
> This is because active-high should be correct if we look at the circuit diagram.
I am loathe to speak for Jess, but I don't think either of us are
disagreeing with your patches. I was just trying to understand why it was
wrong in the first place to see if it was intentionally inverted, or if
there was something that could be improve to stop it happening again.
Apologies if that got lost in translation.
> > Maybe it'd be a bit more foolproof written as "For LEDs that are
> > illuminated while the PWM output is low. For example, where an LED is
> > wired between supply and the PWM output."?
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-18 8:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 8:31 [PATCH 0/2] Change PWM-controlled LED pin active mode and algorithm Nylon Chen
2023-01-13 8:31 ` [PATCH 1/2] riscv: dts: sifive unmatched: Remove PWM controlled LED's active-low properties Nylon Chen
2023-01-17 13:57 ` Conor Dooley
2023-01-13 8:31 ` [PATCH 2/2] pwm: sifive: change the PWM controlled LED algorithm Nylon Chen
2023-01-13 18:32 ` [PATCH 0/2] Change PWM-controlled LED pin active mode and algorithm Conor Dooley
2023-01-13 19:24 ` Jessica Clarke
2023-01-14 14:00 ` Conor Dooley
2023-01-18 2:32 ` Nylon Chen
2023-01-18 8:13 ` Conor Dooley [this message]
2023-01-17 9:32 ` Nylon Chen
2023-01-17 15:08 ` Ron Economos
2023-01-18 1:46 ` Ron Economos
2023-01-18 3:40 ` Ron Economos
2023-01-18 2:30 ` Nylon Chen
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=Y8eqPdifnWbMQI/T@spud \
--to=conor@kernel.org \
--cc=greentime.hu@sifive.com \
--cc=jrtc27@jrtc27.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nylon.chen@sifive.com \
--cc=nylon7717@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vincent.chen@sifive.com \
--cc=zong.li@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox