mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Cc: vkoul@kernel.org, alsa-devel@alsa-project.org,
	pierre-louis.bossart@linux.dev, yung-chuan.liao@linux.intel.com,
	lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
	Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
	venkataprasad.potturu@amd.com, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] ASoC: SOF: amd: pass acp_rev as soundwire resource data
Date: Tue, 24 Sep 2024 11:16:49 +0200	[thread overview]
Message-ID: <ZvKDgcI0DN5Wd8S5@finisterre.sirena.org.uk> (raw)
In-Reply-To: <20240924081846.1834612-4-Vijendar.Mukunda@amd.com>

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

On Tue, Sep 24, 2024 at 01:48:45PM +0530, Vijendar Mukunda wrote:
> Pass acp_rev(ACP pci revision id) as soundwire resource data
> for SoundWire controller probe function.

Acked-by: Mark Brown <broonie@kernel.org>

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

  reply	other threads:[~2024-09-24  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  8:18 [PATCH 0/4] refactor amd soundwire manager driver for acp 6.3 platform Vijendar Mukunda
2024-09-24  8:18 ` [PATCH 1/4] soundwire: amd: pass acp pci revision id as resource data Vijendar Mukunda
2024-09-24  8:18 ` [PATCH 2/4] soundwire: amd: refactor existing code for acp 6.3 platform Vijendar Mukunda
2024-09-24  8:18 ` [PATCH 3/4] ASoC: SOF: amd: pass acp_rev as soundwire resource data Vijendar Mukunda
2024-09-24  9:16   ` Mark Brown [this message]
2024-09-24  8:18 ` [PATCH 4/4] ASoC: amd: ps: pass acp pci revision id " Vijendar Mukunda
2024-09-24  9:17   ` Mark Brown
2024-10-03  8:08 ` [PATCH 0/4] refactor amd soundwire manager driver for acp 6.3 platform Vinod Koul

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=ZvKDgcI0DN5Wd8S5@finisterre.sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=tiwai@suse.com \
    --cc=venkataprasad.potturu@amd.com \
    --cc=vkoul@kernel.org \
    --cc=yung-chuan.liao@linux.intel.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®