From: Johan Hovold <johan@kernel.org>
To: Sibi Sankar <quic_sibis@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>
Cc: sudeep.holla@arm.com, cristian.marussi@arm.com,
konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dmitry.baryshkov@linaro.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, quic_rgottimu@quicinc.com,
quic_kshivnan@quicinc.com, conor+dt@kernel.org,
quic_nkela@quicinc.com, quic_psodagud@quicinc.com,
abel.vesa@linaro.org
Subject: Re: [PATCH V7 0/2] qcom: x1e80100: Enable CPUFreq
Date: Thu, 8 May 2025 14:20:38 +0200 [thread overview]
Message-ID: <aByhln4CpobzSz3s@hovoldconsulting.com> (raw)
In-Reply-To: <20241030130840.2890904-1-quic_sibis@quicinc.com>
Hi Sibi and Bjorn,
On Wed, Oct 30, 2024 at 06:38:38PM +0530, Sibi Sankar wrote:
> This series enables CPUFreq support on the X1E SoC using the SCMI perf
> protocol. This was originally part of the RFC: firmware: arm_scmi:
> Qualcomm Vendor Protocol [1]. I've split it up so that this part can
> land earlier. Warnings Introduced by the series are fixed by [2]
With the SCMI perf quirk for the Qualcomm firmware merged for 6.16, we
can now finally get this one merged.
There appears to be a trivial conflict due to a context change (the new
watchdog node) however.
Can you fix that up when applying, Bjorn, or do you want Sibi to send a
v8?
Johan
next prev parent reply other threads:[~2025-05-08 12:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 13:08 [PATCH V7 0/2] qcom: x1e80100: Enable CPUFreq Sibi Sankar
2024-10-30 13:08 ` [PATCH V7 1/2] arm64: dts: qcom: x1e80100: Add cpucp mailbox and sram nodes Sibi Sankar
2024-10-30 13:08 ` [PATCH V7 2/2] arm64: dts: qcom: x1e80100: Enable cpufreq Sibi Sankar
2024-11-01 13:00 ` [PATCH V7 0/2] qcom: x1e80100: Enable CPUFreq Johan Hovold
2024-11-01 14:08 ` Marc Zyngier
2024-11-01 14:19 ` Johan Hovold
2024-11-01 14:43 ` Marc Zyngier
2024-11-05 16:57 ` Johan Hovold
2024-11-05 18:12 ` Marc Zyngier
2024-12-05 11:23 ` Sibi Sankar
2024-12-05 13:44 ` Marc Zyngier
2024-12-05 15:46 ` Johan Hovold
2025-01-06 12:22 ` Sibi Sankar
2025-01-06 14:57 ` Marc Zyngier
2025-01-10 9:52 ` Johan Hovold
2025-01-17 6:36 ` Sibi Sankar
2025-05-08 12:20 ` Johan Hovold [this message]
2025-05-17 5:57 ` (subset) " 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=aByhln4CpobzSz3s@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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=quic_kshivnan@quicinc.com \
--cc=quic_nkela@quicinc.com \
--cc=quic_psodagud@quicinc.com \
--cc=quic_rgottimu@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
/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