This series add support for sound card on Qualcomm Hawi boards.

This series depends on:
	- https://lore.kernel.org/all/20260712134110.3306763-1-prasad.kumpatla@oss.qualcomm.com/

Prasad Kumpatla (2):
  ASoC: dt-bindings: qcom,sm8250: Add Hawi sound card
  ASoC: qcom: sc8280xp: Add support for Hawi

 .../devicetree/bindings/sound/qcom,sm8250.yaml         |  1 +
 sound/soc/qcom/sc8280xp.c                              | 10 ++++++++++
 2 files changed, 11 insertions(+)


base-commit: bee763d5f341b99cf472afeb508d4988f62a6ca1
prerequisite-patch-id: 28f571976819748d886ecdd32e1ea3976440374b
prerequisite-patch-id: 1b00c4a50852a4058eb2e1e609769ba067fd8d4a
prerequisite-patch-id: 6320a0e2ad587fa5c7fe999ae168689af724a4af
prerequisite-patch-id: 8f084b1c85f92ad8c726a638ef9a28adb6fa517d
prerequisite-patch-id: f34f221540acc83a62421cde5e5d0aeac7b4027e
prerequisite-patch-id: 1025f3d247aff3470afec2790e09909987b94d6b
prerequisite-patch-id: d9710a6c2297f5eabf3433b2763469e8e47c75e3
prerequisite-patch-id: cd11059f673dcc38d9ccfc50f0ebd77d6646f1c6
prerequisite-patch-id: 94805c836fd3766375a7110dfd90f94f48472b07
prerequisite-patch-id: 3b98c7c5d3802ee5c5ad4a11004d05d969dc09a9
-- 
2.34.1

On Mon, Jul 13, 2026 at 11:39:05PM +0530, Prasad Kumpatla wrote:
> This series add support for sound card on Qualcomm Hawi boards.
> 
> This series depends on:
> 	- https://lore.kernel.org/all/20260712134110.3306763-1-prasad.kumpatla@oss.qualcomm.com/

Which is a not directly legible link to "ASoC: qcom: add AudioReach TDM
backend support" which itself has a dependency on some further in flight
stuff also specified as a link to some random message ID with whatever
pile of problems that has.

This isn't directed at you specifically, this is a general problem which
seems to be getting worse and worse with the Qualcomm patches.  There's
multi-level stacks of dependencies, the dependencies are hard to follow
and nothing seems to be moving at any great pace so I'm ending up with
my review queue clogged with things which don't even apply due to the in
flight stuff and it's hard to figure out what's going on.  Can you all
please coordinate with each other and try to get whatever is at the
bottom of these stacks of dependencies in?  If you have to send changes
based on some in flight things specify those dependencies in so they're
readable from the email.  Right now it just seems like there's a
constant stream of stuff being thrown over the wall without any review
going on.

Please include human readable descriptions of things like commits and
issues being discussed in e-mail in your mails, this makes them much
easier for humans to read especially when they have no internet access.
I do frequently catch up on my mail on flights or while otherwise
travelling so this is even more pressing for me than just being about
making things a bit easier to read.

On 7/14/2026 12:52 AM, Mark Brown wrote:
> On Mon, Jul 13, 2026 at 11:39:05PM +0530, Prasad Kumpatla wrote:
>> This series add support for sound card on Qualcomm Hawi boards.
>>
>> This series depends on:
>> 	- https://lore.kernel.org/all/20260712134110.3306763-1-prasad.kumpatla@oss.qualcomm.com/
> Which is a not directly legible link to "ASoC: qcom: add AudioReach TDM
> backend support" which itself has a dependency on some further in flight
> stuff also specified as a link to some random message ID with whatever
> pile of problems that has.
>
> This isn't directed at you specifically, this is a general problem which
> seems to be getting worse and worse with the Qualcomm patches.  There's
> multi-level stacks of dependencies, the dependencies are hard to follow
> and nothing seems to be moving at any great pace so I'm ending up with
> my review queue clogged with things which don't even apply due to the in
> flight stuff and it's hard to figure out what's going on.  Can you all
> please coordinate with each other and try to get whatever is at the
> bottom of these stacks of dependencies in?  If you have to send changes
> based on some in flight things specify those dependencies in so they're
> readable from the email.  Right now it just seems like there's a
> constant stream of stuff being thrown over the wall without any review
> going on.
>
> Please include human readable descriptions of things like commits and
> issues being discussed in e-mail in your mails, this makes them much
> easier for humans to read especially when they have no internet access.
> I do frequently catch up on my mail on flights or while otherwise
> travelling so this is even more pressing for me than just being about
> making things a bit easier to read.

Hi Mark,

Thank you for the feedback and for highlighting this broader issue.

That's a fair point. I'll update the cover letter to include concise,
human-readable descriptions of the dependency chain and the purpose of
each prerequisite series, rather than relying solely on lore links.

I appreciate the guidance and will incorporate this in the next revision.

Thanks,
Prasad

On 7/13/26 8:22 PM, Mark Brown wrote:
> On Mon, Jul 13, 2026 at 11:39:05PM +0530, Prasad Kumpatla wrote:
>> This series add support for sound card on Qualcomm Hawi boards.
>>
>> This series depends on:
>> 	- https://lore.kernel.org/all/20260712134110.3306763-1-prasad.kumpatla@oss.qualcomm.com/
> 
> Which is a not directly legible link to "ASoC: qcom: add AudioReach TDM
> backend support" which itself has a dependency on some further in flight
> stuff also specified as a link to some random message ID with whatever
> pile of problems that has.
> 
> This isn't directed at you specifically, this is a general problem which
> seems to be getting worse and worse with the Qualcomm patches.  There's
> multi-level stacks of dependencies, the dependencies are hard to follow
> and nothing seems to be moving at any great pace so I'm ending up with
> my review queue clogged with things which don't even apply due to the in
> flight stuff and it's hard to figure out what's going on.  Can you all
> please coordinate with each other and try to get whatever is at the
> bottom of these stacks of dependencies in?  If you have to send changes
> based on some in flight things specify those dependencies in so they're
> readable from the email.  Right now it just seems like there's a
> constant stream of stuff being thrown over the wall without any review
> going on.

Sorry Mark about this mess and I agree with your statement about both
reviews and flood of patches with multiple dependencies send by
different engineers.

I will try to fix the review side (bring in more people) and make sure
that some of these series endups in a maintainer friendly way.

--srini
> 
> Please include human readable descriptions of things like commits and
> issues being discussed in e-mail in your mails, this makes them much
> easier for humans to read especially when they have no internet access.
> I do frequently catch up on my mail on flights or while otherwise
> travelling so this is even more pressing for me than just being about
> making things a bit easier to read.