From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Alexandru Gagniuc <mr.nuke.me@gmail.com>,
andersson@kernel.org, mathieu.poirier@linaro.org,
krzk+dt@kernel.org,
Gokul Sriram Palanisamy <quic_gokulsri@quicinc.com>,
Govind Singh <govinds@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/9] remoteproc: qcom_q6v5_wcss: drop unused clocks from q6v5 struct
Date: Fri, 19 Dec 2025 14:31:07 +0100 [thread overview]
Message-ID: <f4cd079b-0b44-4ea8-9aa9-9bfaa4c2d03f@oss.qualcomm.com> (raw)
In-Reply-To: <20251219043425.888585-8-mr.nuke.me@gmail.com>
On 12/19/25 5:34 AM, Alexandru Gagniuc wrote:
> Three of the clocks from struct q6v5_wcss are not populated, and are
> not used. Remove them.
>
> Fixes: 0af65b9b915e ("remoteproc: qcom: wcss: Add non pas wcss Q6 support for QCS404")
>
> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
> ---
It's worth noting they are handled by the driver through register accesses
to the Q6 regspace
This patch can be moved to #1 so that Bjorn can pick it up independently
Konrad
next prev parent reply other threads:[~2025-12-19 13:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 4:34 [PATCH 1/9] dt-bindings: remoteproc: qcom,ipq8074-wcss-pil: convert to DT schema Alexandru Gagniuc
2025-12-19 4:34 ` [PATCH 2/9] dt-bindings: remoteproc: qcom: add IPQ9574 image loader Alexandru Gagniuc
2025-12-19 5:37 ` Rob Herring (Arm)
2025-12-19 14:44 ` Rob Herring
2025-12-20 8:54 ` Krzysztof Kozlowski
2025-12-23 19:45 ` Alex G.
2025-12-20 8:56 ` Krzysztof Kozlowski
2025-12-19 4:34 ` [PATCH 3/9] dt-bindings: clock: gcc-ipq9574: add wcss remoteproc clocks Alexandru Gagniuc
2025-12-19 4:34 ` [PATCH 4/9] arm64: dts: qcom: ipq9574: add wcss remoteproc nodes Alexandru Gagniuc
2025-12-19 13:43 ` Konrad Dybcio
2025-12-19 4:34 ` [PATCH 5/9] clk: qcom: gcc-ipq9574: add wcss remoteproc clocks Alexandru Gagniuc
2025-12-19 4:34 ` [PATCH 6/9] remoteproc: qcom_q6v5_wcss: support IPQ9574 Alexandru Gagniuc
2025-12-19 13:20 ` Konrad Dybcio
2025-12-23 20:21 ` Alex G.
2025-12-24 9:44 ` Vignesh Viswanathan
2025-12-24 17:36 ` Alex G.
2025-12-29 12:35 ` Konrad Dybcio
2026-01-05 16:09 ` mr.nuke.me
2026-01-05 17:57 ` Vignesh Viswanathan
2026-01-07 13:26 ` Konrad Dybcio
2026-01-07 18:25 ` Vignesh Viswanathan
2025-12-19 4:34 ` [PATCH 7/9] remoteproc: qcom_q6v5_wcss: support m3 firmware Alexandru Gagniuc
2025-12-19 13:29 ` Konrad Dybcio
2025-12-23 20:35 ` Alex G.
2025-12-29 12:37 ` Konrad Dybcio
2026-01-05 15:23 ` mr.nuke.me
2026-01-05 18:00 ` Vignesh Viswanathan
2026-01-07 11:55 ` Konrad Dybcio
2025-12-19 4:34 ` [PATCH 8/9] remoteproc: qcom_q6v5_wcss: drop unused clocks from q6v5 struct Alexandru Gagniuc
2025-12-19 13:31 ` Konrad Dybcio [this message]
2025-12-19 4:34 ` [PATCH 9/9] remoteproc: qcom_q6v5_wcss: use bulk clk API for q6 clocks in QCS404 Alexandru Gagniuc
2025-12-19 14:52 ` [PATCH 1/9] dt-bindings: remoteproc: qcom,ipq8074-wcss-pil: convert to DT schema Krzysztof Kozlowski
2025-12-20 18:40 ` Alex G.
2025-12-19 16:49 ` Rob Herring
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=f4cd079b-0b44-4ea8-9aa9-9bfaa4c2d03f@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=govinds@codeaurora.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mr.nuke.me@gmail.com \
--cc=quic_gokulsri@quicinc.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