Re: [PATCH v6 0/5] Subject: [PATCH v6 0/7] ASoC: qcom and pinctrl: add LPASS LPR voting and Hawi LPASS LPI support

Mark Brown <[email protected]> Thu, 30 Jul 2026 01:22:08 +0100

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	<[email protected]>

On Fri, Jul 24, 2026 at 07:32:55AM -0700, Bartosz Golaszewski wrote:
> On Fri, 24 Jul 2026 16:17:03 +0200, Prasad Kumpatla

> > The intended merge strategy is:

> >   1. Merge the dt-bindings patch adding LPASS_HW_LPR_VOTE to
> >      qcom,q6dsp-lpass-ports.h.

> >   2. After the header update is merged, the remaining ASoC and
> >      pinctrl patches may be merged through their respective
> >      subsystem trees.

> Do you really want to wait an entire additional cycle for a one-liner to first
> get upstream? I mean: I don't mind it but it's a weird strategy.

I presume the thought is to put it on a shared branch, but that gets
problematic if I create that branch because the ASoC driver has
dependencies on whatever is in the huge pile of stuff that's already
going through ASoC so it'd pull in my entire history.  I suppose I could
do the tag, merge it into my branch then apply the ASoC driver?

I've complained previously about how unmanagable all these
interdependent qcom things are, now this adds cross tree issues!

signature.asc (application/pgp-signature, 488 B)