All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: (subset) [PATCH 0/8] qcom-cpufreq-hw binding improvements
Date: Wed, 22 Mar 2023 07:45:09 -0700	[thread overview]
Message-ID: <167949631653.1081726.15984867720732341048.b4-ty@kernel.org> (raw)
In-Reply-To: <20230308-topic-cpufreq_bindings-v1-0-3368473ec52d@linaro.org>

On Wed, 08 Mar 2023 02:26:57 +0100, Konrad Dybcio wrote:
> This series tries to better sanitize what's actually allowed on which
> SoC and lowers the minimum frequency domain count to 1, as that's what's
> present on at least QCM2290.
> 
> 

Applied, thanks!

[4/8] arm64: dts: qcom: sc7180: Add SoC-specific compatible to cpufreq_hw
      commit: e4c17be956fbe133211c24b9fc9ba253ffc44db6
[5/8] arm64: dts: qcom: sdm845: Add SoC-specific compatible to cpufreq_hw
      commit: 236e7dd568ed4b839fb8abdf3ce7c77444e610e2
[6/8] arm64: dts: qcom: sm6115: Add SoC-specific compatible to cpufreq_hw
      commit: f33f95773e148cd0adbfc3135f2bfbf56a69f488
[7/8] arm64: dts: qcom: sm6350: Add SoC-specific compatible to cpufreq_hw
      commit: 64917707914f95fa5827f2cc5bea2d5febe3a01b
[8/8] arm64: dts: qcom: sm8150: Add SoC-specific compatible to cpufreq_hw
      commit: b2e1f87070ead06fb2918edeeed4329f58d1b2ee

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

  parent reply	other threads:[~2023-03-22 14:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  1:26 [PATCH 0/8] qcom-cpufreq-hw binding improvements Konrad Dybcio
2023-03-08  1:26 ` [PATCH 1/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Allow just 1 frequency domain Konrad Dybcio
2023-03-16 22:36   ` Rob Herring
2023-03-08  1:26 ` [PATCH 2/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Sanitize data per compatible Konrad Dybcio
2023-03-16 22:39   ` Rob Herring
2023-03-08  1:27 ` [PATCH 3/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Add QCM2290 Konrad Dybcio
2023-03-16 22:39   ` Rob Herring
2023-03-08  1:27 ` [PATCH 4/8] arm64: dts: qcom: sc7180: Add SoC-specific compatible to cpufreq_hw Konrad Dybcio
2023-03-08  1:27 ` [PATCH 5/8] arm64: dts: qcom: sdm845: " Konrad Dybcio
2023-03-08  1:27 ` [PATCH 6/8] arm64: dts: qcom: sm6115: " Konrad Dybcio
2023-03-08  1:27 ` [PATCH 7/8] arm64: dts: qcom: sm6350: " Konrad Dybcio
2023-03-08 10:35   ` Luca Weiss
2023-03-08  1:27 ` [PATCH 8/8] arm64: dts: qcom: sm8150: " Konrad Dybcio
2023-03-22 14:45 ` Bjorn Andersson [this message]
2023-03-30  3:59 ` [PATCH 0/8] qcom-cpufreq-hw binding improvements Viresh Kumar

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=167949631653.1081726.15984867720732341048.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.