From: Bjorn Andersson <andersson@kernel.org>
To: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Marijn Suijten <marijn.suijten@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 0/3] More RPMhPD levels + sm8550
Date: Fri, 19 May 2023 19:01:24 -0700 [thread overview]
Message-ID: <168454808160.2842337.12287707566095048911.b4-ty@kernel.org> (raw)
In-Reply-To: <20230517-topic-kailua-rpmhpd-v2-0-3063ce19c491@linaro.org>
On Wed, 17 May 2023 22:12:49 +0200, Konrad Dybcio wrote:
> Bring in missing RPMhPd levels from downstream and add ones we'll
> need for GPU on SM8550.
>
> Patch 1 adds the missing ones with an easy-to-read diff, patch 2
> reformats the block and patch 3 adds the necessary levels to 8550 dt.
>
>
> [...]
Applied, thanks!
[1/3] dt-bindings: power: qcom,rpmpd: add missing RPMH levels
commit: 4755e880b08d963db24a1b3a710ee0e62f36aa49
[2/3] dt-bindings: power: qcom,rpmpd: Format RPMh levels better
commit: 1738600082987ddcf9cfce753ae3c581c8e46933
[3/3] arm64: dts: qcom: sm8550: Add missing RPMhPD OPP levels
commit: 99d33ee61cb06e1235dab404b33d4694fe18088f
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-05-20 1:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 20:12 Konrad Dybcio
2023-05-17 20:12 ` [PATCH v2 1/3] dt-bindings: power: qcom,rpmpd: add missing RPMH levels Konrad Dybcio
2023-05-18 0:40 ` Dmitry Baryshkov
2023-05-17 20:12 ` [PATCH v2 2/3] dt-bindings: power: qcom,rpmpd: Format RPMh levels better Konrad Dybcio
2023-05-17 20:12 ` [PATCH v2 3/3] arm64: dts: qcom: sm8550: Add missing RPMhPD OPP levels Konrad Dybcio
2023-05-18 0:41 ` Dmitry Baryshkov
2023-05-20 2:01 ` Bjorn Andersson [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=168454808160.2842337.12287707566095048911.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.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
all inboxes | Powered by JetHome®