mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
To: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>,
	Srinivas Kandagatla <srini@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, ajay.nandam@oss.qualcomm.com
Subject: Re: [PATCH v2 0/2] This series resends the self-contained ASoC changes from the earlier Hawi/Maili LPASS audio submission.
Date: Wed, 14 Oct 2026 15:42:48 +0530	[thread overview]
Message-ID: <47290c05-bf04-4f38-8061-e1d7f9815e96@oss.qualcomm.com> (raw)
In-Reply-To: <20261009111719.2609060-1-prasad.kumpatla@oss.qualcomm.com>



On 10/9/2026 4:47 PM, Prasad Kumpatla wrote:
> Hi,
> 
> The original v1 series included bindings, devicetree and defconfig changes
> which either depend on other LPASS macro/platform updates or need to be
> handled with the corresponding platform enablement. Keep this revision scoped
> to the two ASoC changes which are independent and can be reviewed/applied
> separately.
> 
> The October 6 subset was incorrectly posted as v1. This v2 supersedes that
> posting and keeps the revision history tied to the original September 23 v1
> series.

LGTM

Reviewed-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>

Tested-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>


> 
> Previous submissions:
> v1:
>    https://lore.kernel.org/all/20260923084627.748920-1-prasad.kumpatla@oss.qualcomm.com/
> incorrectly-numbered subset:
>    https://lore.kernel.org/all/20261006053717.3455143-1-prasad.kumpatla@oss.qualcomm.com/
> 
> ---
> Changes in v2:
> - Correct the revision number. These patches were previously posted as part
>    of the September 23 v1 Hawi/Maili audio series; the October 6 subset was
>    incorrectly labelled v1.
> - Drop the Maili LPASS macro binding and Hawi/Maili DTS patches from this
>    series because they depend on other platform/audio changes still being
>    reviewed.
> - Drop the arm64 defconfig patch from this series. That patch belongs with
>    the Hawi/Maili platform enablement and needs a separate rationale if it is
>    reposted.
> - Keep only the two independent ASoC patches.
> 
> Prasad Kumpatla (2):
>    ASoC: codecs: wsa885x: Reset registers on teardown for B2B playback
>    ASoC: qcom: sc8280xp: add Maili sound card configuration
> 
>   sound/soc/codecs/wsa885x.c | 11 ++++++++++-
>   sound/soc/qcom/sc8280xp.c  | 11 ++++++++++-
>   2 files changed, 20 insertions(+), 2 deletions(-)
> 


      parent reply	other threads:[~2026-10-14 10:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 11:17 Prasad Kumpatla
2026-10-09 11:17 ` [PATCH v2 1/2] ASoC: codecs: wsa885x: Reset registers on teardown for B2B playback Prasad Kumpatla
2026-10-09 11:17 ` [PATCH v2 2/2] ASoC: qcom: sc8280xp: add Maili sound card configuration Prasad Kumpatla
2026-10-14 10:12 ` Ajay Kumar Nandam [this message]

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=47290c05-bf04-4f38-8061-e1d7f9815e96@oss.qualcomm.com \
    --to=ajay.nandam@oss.qualcomm.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=prasad.kumpatla@oss.qualcomm.com \
    --cc=srini@kernel.org \
    --cc=tiwai@suse.com \
    /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

all inboxes | Powered by JetHome®