On 2/18/2026 3:44 PM, Dmitry Baryshkov wrote:

On Wed, Feb 18, 2026 at 06:59:05AM +0000, Antony Kurniawan Soemardi wrote:

quoted

Document the qcom,rpmcc-msm8960 compatible.

The MSM8960 platform shares the same RPM clock definitions as
APQ8064, so extend the existing conditional schema to treat
qcom,rpmcc-msm8960 the same as qcom,rpmcc-apq8064.

The way you implemented it, it requires driver changes which were not
included in this PR.

Oh wait sorry, I was misremembering thing about how I should sent
dt-binding patches. I'm planning to send the following patches:

dt-bindings: clock: qcom,rpmcc: add msm8960 compatible
dt-bindings: mfd: syscon: add qcom,msm8960-sps-sic
mfd: qcom_rpm: add msm8960 QDSS clock resource
clk: qcom: clk-rpm: add msm8960 compatible
ARM: dts: qcom: msm8960: add rpm clock controller node
ARM: dts: qcom: msm8960: add scm node
ARM: dts: qcom: msm8960: add smem & hwmutex nodes
ARM: dts: qcom: msm8960: add smsm & sps nodes
ARM: dts: qcom: msm8960: add riva nodes
ARM: dts: qcom: msm8960: huashan: add riva node

I'm concerned that this might be too large? Or not?

Would it be better to submit them as a single patch series to enable
Bluetooth and Wi-Fi on msm8960?

also +Krzysztof for the same comment.

Thanks,
Antony K. S.