From: Lee Jones <lee@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Antony Kurniawan Soemardi <linux@smankusors.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org,
Rudraksha Gupta <guptarud@gmail.com>
Subject: Re: (subset) [PATCH v2 03/10] mfd: qcom_rpm: add msm8960 QDSS clock resource
Date: Thu, 21 May 2026 14:04:35 +0100 [thread overview]
Message-ID: <177936867589.3586629.11413200027317835778.b4-ty@b4> (raw)
In-Reply-To: <20260514-msm8960-wifi-v2-3-7cbae45dab5e@smankusors.com>
On Thu, 14 May 2026 21:08:32 +0700, Antony Kurniawan Soemardi wrote:
> The msm8960 RPM resource table is missing the QDSS clock entry (resource
> ID 209) that is present in the android-msm-mako-3.4 downstream kernel.
> Add it so that RPM clock initialization succeeds.
Applied, thanks!
[03/10] mfd: qcom_rpm: add msm8960 QDSS clock resource
commit: 72c793196d12cb27e192dee77c3ea64c755b7687
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-05-21 13:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 14:08 [PATCH v2 00/10] ARM: qcom: msm8960: enable WCNSS (Bluetooth & Wi-Fi) Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 01/10] dt-bindings: clock: qcom,rpmcc: add msm8960 compatible Antony Kurniawan Soemardi via B4 Relay
2026-05-15 6:56 ` Krzysztof Kozlowski
2026-05-14 14:08 ` [PATCH v2 02/10] dt-bindings: mfd: syscon: add qcom,msm8960-sps-sic Antony Kurniawan Soemardi via B4 Relay
2026-05-14 19:40 ` sashiko-bot
2026-05-15 6:57 ` Krzysztof Kozlowski
2026-05-14 14:08 ` [PATCH v2 03/10] mfd: qcom_rpm: add msm8960 QDSS clock resource Antony Kurniawan Soemardi via B4 Relay
2026-05-21 13:04 ` Lee Jones [this message]
2026-05-14 14:08 ` [PATCH v2 04/10] clk: qcom: clk-rpm: add msm8960 compatible Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 05/10] ARM: dts: qcom: msm8960: add RPM clock controller and fix USB clocks Antony Kurniawan Soemardi via B4 Relay
2026-05-14 21:01 ` sashiko-bot
2026-05-14 14:08 ` [PATCH v2 06/10] ARM: dts: qcom: msm8960: add SCM Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 07/10] ARM: dts: qcom: msm8960: add SMEM & hwlock Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 08/10] ARM: dts: qcom: msm8960: add SMSM & SPS Antony Kurniawan Soemardi via B4 Relay
2026-05-14 21:41 ` sashiko-bot
2026-05-14 14:08 ` [PATCH v2 09/10] ARM: dts: qcom: msm8960: add Riva Antony Kurniawan Soemardi via B4 Relay
2026-05-14 14:08 ` [PATCH v2 10/10] ARM: dts: qcom: msm8960: huashan: enable Wi-Fi and Bluetooth Antony Kurniawan Soemardi via B4 Relay
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=177936867589.3586629.11413200027317835778.b4-ty@b4 \
--to=lee@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guptarud@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@smankusors.com \
--cc=mturquette@baylibre.com \
--cc=phone-devel@vger.kernel.org \
--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