Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	quic_rohkumar@quicinc.com, linux-arm-msm@vger.kernel.org,
	swboyd@chromium.org, tiwai@suse.com, lgirdwood@gmail.com,
	robh+dt@kernel.org, bjorn.andersson@linaro.org,
	agross@kernel.org, srinivas.kandagatla@linaro.org,
	bgoswami@quicinc.com, quic_plai@quicinc.com,
	judyhsiao@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: google: dt-bindings: Update sc7280-audioreach-herobrine compatible name
Date: Wed, 22 Jun 2022 13:46:46 +0100	[thread overview]
Message-ID: <YrMPNpE+RWIZP372@sirena.org.uk> (raw)
In-Reply-To: <1655892799-29641-2-git-send-email-quic_srivasam@quicinc.com>

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

On Wed, Jun 22, 2022 at 03:43:18PM +0530, Srinivasa Rao Mandadapu wrote:
> Update audioreach based compatible string for sc7280 based ADSP enabled
> platforms.

>    compatible:
>      enum:
>        - google,sc7280-herobrine
> +      - google,sc7280-audioreach-herobrine

Isn't the DSP firmware selection a purely software one?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-06-22 12:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 10:13 [PATCH 0/2] Update machine driver for audioreach solution Srinivasa Rao Mandadapu
2022-06-22 10:13 ` [PATCH 1/2] ASoC: google: dt-bindings: Update sc7280-audioreach-herobrine compatible name Srinivasa Rao Mandadapu
2022-06-22 12:46   ` Mark Brown [this message]
2022-06-27  3:59     ` Srinivasa Rao Mandadapu
2022-06-22 10:13 ` [PATCH 2/2] ASoC: qcom: Add driver support for audioreach solution Srinivasa Rao Mandadapu

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=YrMPNpE+RWIZP372@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=agross@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bgoswami@quicinc.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=judyhsiao@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_plai@quicinc.com \
    --cc=quic_rohkumar@quicinc.com \
    --cc=quic_srivasam@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=swboyd@chromium.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