devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ansuel Smith <ansuelsmth@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock
Date: Fri, 29 Apr 2022 17:12:13 +0200	[thread overview]
Message-ID: <626c00df.1c69fb81.a5445.4d7c@mx.google.com> (raw)
In-Reply-To: <f260cf81-9db9-710b-1242-45a232e7c7c4@linaro.org>

On Fri, Apr 29, 2022 at 06:11:21PM +0300, Dmitry Baryshkov wrote:
> On 29/04/2022 15:29, Ansuel Smith wrote:
> > Replace gcc PXO phandle to pxo_board fixed clock declared in the dts.
> > gcc driver doesn't provide PXO_SRC as it's a fixed-clock. This cause a
> > kernel panic if any driver actually try to use it.
> > 
> > Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
> 
> Fixes: 40cf5c884a96 ("ARM: dts: qcom: add L2CC and RPM for IPQ8064")
> 
> It would be nice if you add Fixes tags to your patches in future. Fixes tags
> allow picking up patches for stable/LTS trees.
> 
> For these two patches I'd suggest reordering them. A fix should go first
> (you'll have to define pxa_board label in it). It can then be accepted into
> other kernel without dependency on the other patch.
> 
> The gcc patch will come next, it will define cxo_board label and use both
> clocks in the gcc node. It is not fixing a bug, so there is no need about
> backporting it.
> 
> Generic rule: fixes go first (in the patch series), so that they have
> minimum inter-dependencies.
>

Didn't know about this. Thanks for the hint! Will do the change.

> > ---
> >   arch/arm/boot/dts/qcom-ipq8064.dtsi | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/arch/arm/boot/dts/qcom-ipq8064.dtsi b/arch/arm/boot/dts/qcom-ipq8064.dtsi
> > index 9817448cfa95..ad30f7c8a5a7 100644
> > --- a/arch/arm/boot/dts/qcom-ipq8064.dtsi
> > +++ b/arch/arm/boot/dts/qcom-ipq8064.dtsi
> > @@ -784,7 +784,7 @@ tcsr: syscon@1a400000 {
> >   		l2cc: clock-controller@2011000 {
> >   			compatible = "qcom,kpss-gcc", "syscon";
> >   			reg = <0x2011000 0x1000>;
> > -			clocks = <&gcc PLL8_VOTE>, <&gcc PXO_SRC>;
> > +			clocks = <&gcc PLL8_VOTE>, <&pxo_board>;
> >   			clock-names = "pll8_vote", "pxo";
> >   			clock-output-names = "acpu_l2_aux";
> >   		};
> 
> 
> -- 
> With best wishes
> Dmitry

-- 
	Ansuel

      reply	other threads:[~2022-04-29 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 12:29 [PATCH 0/2] PXO fixes for ipq8064 dtsi Ansuel Smith
2022-04-29 12:29 ` [PATCH 1/2] ARM: dts: qcom: add syscon and cxo/pxo clock to gcc node for ipq8064 Ansuel Smith
2022-04-29 12:29 ` [PATCH 2/2] ARM: dts: qcom: replace gcc PXO with pxo_board fixed clock Ansuel Smith
2022-04-29 15:11   ` Dmitry Baryshkov
2022-04-29 15:12     ` Ansuel Smith [this message]

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=626c00df.1c69fb81.a5445.4d7c@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).