From: Johan Hovold <johan@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Mark Brown <broonie@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: clock: qcom: add SA8540P gpucc
Date: Tue, 26 Mar 2024 17:40:28 +0100 [thread overview]
Message-ID: <ZgL6fE8bFx7H41kr@hovoldconsulting.com> (raw)
In-Reply-To: <a6fbbfd3-516b-4269-b4b2-611979b62fd7@kernel.org>
On Tue, Mar 26, 2024 at 04:59:43PM +0100, Krzysztof Kozlowski wrote:
> On 26/03/2024 15:01, Johan Hovold wrote:
> > The SA8540P platform is closely related to SC8280XP but differs in that
> > it uses an external supply for the GX power domain.
> >
> > Add a new compatible string for the SA8540P GPU clock controller so that
> > the OS can determine which resources to look for.
> >
> > Fixes: e60b95d2b687 ("dt-bindings: clock: qcom: Allow VDD_GFX supply to GX")
>
> I don't get why adding new device support is a fix. Commit msg did not
> help me to understand it.
Yeah, perhaps I could have expanded on the problem a bit more here.
Hopefully it's clear if you look at the cover letter, but the commit
referred to above should have added a new compatible for SA8540P which
uses the new supply so that the OS can determine when it should try to
look it up and when it is required.
The Fixes tag can also be dropped, I admit this is not clear-cut.
> > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> > ---
> > Documentation/devicetree/bindings/clock/qcom,gpucc.yaml | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/Documentation/devicetree/bindings/clock/qcom,gpucc.yaml b/Documentation/devicetree/bindings/clock/qcom,gpucc.yaml
> > index f57aceddac6b..5b385e4976b6 100644
> > --- a/Documentation/devicetree/bindings/clock/qcom,gpucc.yaml
> > +++ b/Documentation/devicetree/bindings/clock/qcom,gpucc.yaml
> > @@ -28,6 +28,7 @@ properties:
> > compatible:
> > enum:
> > - qcom,sdm845-gpucc
> > + - qcom,sa8540p-gpucc
>
> This looks fine and pretty trivial, but I really do not understand why
> skipping our list for automated testing.
>
> <standard letter>
...
> </standard letter>
Spare me the rant. This was obviously a mistake from reusing and
manually amending a git-send-email command from shell history and
failing to notice that this series also should have been CCed the
devicetree list.
Johan
next prev parent reply other threads:[~2024-03-26 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 14:01 [PATCH 0/5] clk: qcom: gpucc-sc8280xp: fix GX external supply lookup Johan Hovold
2024-03-26 14:01 ` [PATCH 1/5] dt-bindings: clock: qcom: add SA8540P gpucc Johan Hovold
2024-03-26 15:59 ` Krzysztof Kozlowski
2024-03-26 16:40 ` Johan Hovold [this message]
2024-03-27 8:54 ` Krzysztof Kozlowski
2024-03-28 15:43 ` Johan Hovold
2024-03-26 14:01 ` [PATCH 2/5] arm64: dts: qcom: sa8540p: use sa8540p gpucc compatible Johan Hovold
2024-03-26 16:02 ` Krzysztof Kozlowski
2024-03-26 16:48 ` Johan Hovold
2024-03-26 14:01 ` [PATCH 3/5] clk: qcom: gpucc-sc8280xp: make cc descriptor const Johan Hovold
2024-03-26 20:45 ` Konrad Dybcio
2024-03-26 14:01 ` [PATCH 4/5] clk: qcom: gpucc-sc8280xp: fix GX external supply lookup Johan Hovold
2024-03-26 14:01 ` [PATCH 5/5] arm64: dts: qcom: sa8540p: drop fallback gpucc compatible Johan Hovold
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=ZgL6fE8bFx7H41kr@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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