Re: [PATCH v5 0/4] ASoC: qcom and pinctrl: add LPASS LPR voting and Hawi LPASS LPI TLMM

Bartosz Golaszewski <[email protected]>
Newsgroups org.kernel.vger.linux-gpio,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-sound
Message-ID <CAMRc=MddF5CzMgkUeCWbMFw=J3ZvbxK3qm0-oqvnaHFK61SKNw@mail.gmail.com>
On Wed, 22 Jul 2026 14:02:13 +0200, Prasad Kumpatla
<[email protected]> said:
> This series adds support for LPASS low-power resource (LPR) voting
> through PRM and introduces LPASS LPI TLMM pinctrl support for newer
> platforms such as Hawi.
>
> On such platforms, LPASS requires LPR resource voting via PRM to keep
> the subsystem active. This is handled by adding a new clock ID and
> support for PARAM_ID_RSC_CPU_LPR in q6prm.
>
> Additionally, a new LPASS LPI TLMM block is introduced, requiring a
> dedicated DT binding and pinctrl driver.
>
> Dependencies and merge strategy
> ===============================
>
> The series introduces a new clock identifier, LPASS_HW_LPR_VOTE, in
> qcom,q6dsp-lpass-ports.h. This clock ID is consumed both by the ASoC
> LPASS LPR voting support and by the Hawi LPASS LPI DT binding.
>
> As a result, the DT binding header update introducing
> LPASS_HW_LPR_VOTE is the only cross-subsystem dependency in this
> series.
>
> The intended merge strategy is:
>
>   1. Merge the LPASS_HW_LPR_VOTE definition in
>      qcom,q6dsp-lpass-ports.h.
>
>   2. Merge the ASoC LPASS LPR voting support via the ASoC tree.
>
>   3. Merge the Hawi LPASS LPI DT binding and pinctrl driver via the
>      pinctrl tree.
>
> Apart from the shared DT binding header update, the ASoC and pinctrl
> changes are independent and do not introduce additional build-time
> dependencies between the two subsystems.

But that was my question all along. If I take only patches 3 and 4,
`make dt_bindings_check` will not work in my tree. Krzysztof: do we not care
about make dt_bindings_check in linux-next?

Thanks,
Bartosz
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.