From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: lgirdwood@gmail.com, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.dev, peter.ujfalusi@linux.intel.com,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH 2/3] ASoC: SDCA: Remove sdca_function_data duplication
Date: Tue, 28 Apr 2026 08:25:26 +0900 [thread overview]
Message-ID: <ae_wZiInOgauLyPx@sirena.co.uk> (raw)
In-Reply-To: <20260427115925.3801099-3-ckeepax@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
On Mon, Apr 27, 2026 at 12:59:24PM +0100, Charles Keepax wrote:
> The class driver internally has an array of sdca_function_data pointers
> that it uses to store the parsed DisCo data. However, there is already
> an sdca_function_data attached to the auxdev device. It makes more sense
> }
>
> int sdca_parse_function(struct device *dev, struct sdw_slave *sdw,
> - struct sdca_function_desc *desc,
> struct sdca_function_data *function);
>
This will need a rebase for the tas2783 driver.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-27 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 11:59 [PATCH 0/3] Improve SDCA support for duplicated features Charles Keepax
2026-04-27 11:59 ` [PATCH 1/3] ASoC: SDCA: Add correct masks whilst reporting SDCA jack status Charles Keepax
2026-04-28 20:18 ` Pierre-Louis Bossart
2026-04-29 13:10 ` Charles Keepax
2026-04-30 8:11 ` Pierre-Louis Bossart
2026-04-27 11:59 ` [PATCH 2/3] ASoC: SDCA: Remove sdca_function_data duplication Charles Keepax
2026-04-27 23:25 ` Mark Brown [this message]
2026-04-27 11:59 ` [PATCH 3/3] ASoC: SDCA: Support devices with multiple functions of identical type Charles Keepax
2026-04-27 23:27 ` Mark Brown
2026-04-28 8:26 ` Charles Keepax
2026-04-30 8:09 ` [PATCH 0/3] Improve SDCA support for duplicated features Pierre-Louis Bossart
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=ae_wZiInOgauLyPx@sirena.co.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--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