linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Weiss <luca@z3ntu.xyz>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: [PATCH 1/2] ARM: dts: qcom: Add LPG node to pm8941
Date: Mon, 16 May 2022 22:09:47 +0200	[thread overview]
Message-ID: <2629354.mvXUDI8C0e@g550jk> (raw)
In-Reply-To: <YnSazu3rcBMFPxYw@builder.lan>

Hi Bjorn,

On Freitag, 6. Mai 2022 05:49:34 CEST Bjorn Andersson wrote:
> On Thu 05 May 03:01 CDT 2022, Luca Weiss wrote:
> > Hi Bjorn,
> > 
> > On Mittwoch, 4. Mai 2022 22:54:10 CEST Bjorn Andersson wrote:
> > > The PM8941 contains 8 LPG channels, as well as TRILED and LUT blocks.
> > > Add a node for these.
> > > 
> > > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > > ---
> > > 
> > >  arch/arm/boot/dts/qcom-pm8941.dtsi | 9 +++++++++
> > >  1 file changed, 9 insertions(+)
> > > 
> > > diff --git a/arch/arm/boot/dts/qcom-pm8941.dtsi
> > > b/arch/arm/boot/dts/qcom-pm8941.dtsi index cdd2bdb77b32..7881a071b372
> > > 100644
> > > --- a/arch/arm/boot/dts/qcom-pm8941.dtsi
> > > +++ b/arch/arm/boot/dts/qcom-pm8941.dtsi
> > > @@ -144,6 +144,15 @@ pm8941_1: pm8941@1 {
> > > 
> > >  		#address-cells = <1>;
> > >  		#size-cells = <0>;
> > > 
> > > +		pm8941_lpg: lpg {
> > > +			compatible = "qcom,pm8941-lpg";
> > > +
> > > +			#address-cells = <1>;
> > > +			#size-cells = <0>;
> > 
> > Just curious, why doesn't pm8941 have #pwm-cells = <2>; like the other lpg
> > nodes in [0]?
> 
> I guess I didn't have a need for the lpg to be a pwm-chip on this pmic,
> yet. This could be added now, or at a later point when someone has a
> usecase for the pwm-chip.

While I don't know the use case for using the lpg as pwm on consumer hardware, 
it's maybe a good idea to add now?

> 
> > Other than that, the node works fine on pm8941. Will send a patch for
> > enabling notification LED on msm8974-FP2 soon.
> 
> If you turn that into a Tested-by, and preferably a Reviewed-by, I would
> have what I need to merge the two changes.

In any case:

Tested-by: Luca Weiss <luca@z3ntu.xyz>
Reviewed-by: Luca Weiss <luca@z3ntu.xyz>

Regards
Luca

> 
> Looking forward to the FP2 patch.
> 
> Thanks,
> Bjorn
> 
> > Regards
> > Luca
> > 
> > [0]
> > https://lore.kernel.org/linux-arm-msm/20220505022706.1692554-2-bjorn.ande
> > rsson@linaro.org/> 
> > > +
> > > +			status = "disabled";
> > > +		};
> > > +
> > > 
> > >  		pm8941_wled: wled@d800 {
> > >  		
> > >  			compatible = "qcom,pm8941-wled";
> > >  			reg = <0xd800>;





  reply	other threads:[~2022-05-16 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 20:54 [PATCH 1/2] ARM: dts: qcom: Add LPG node to pm8941 Bjorn Andersson
2022-05-04 20:54 ` [PATCH 2/2] ARM: dts: qcom: msm8974-sony: Enable LPG Bjorn Andersson
2022-05-11 19:36   ` Konrad Dybcio
2022-05-05  8:01 ` [PATCH 1/2] ARM: dts: qcom: Add LPG node to pm8941 Luca Weiss
2022-05-06  3:49   ` Bjorn Andersson
2022-05-16 20:09     ` Luca Weiss [this message]
2022-07-17  3:08 ` Bjorn Andersson

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=2629354.mvXUDI8C0e@g550jk \
    --to=luca@z3ntu.xyz \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).