From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: lgirdwood@gmail.com, pierre-louis.bossart@linux.dev,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH v6 0/7] Add DAPM/ASoC helpers to create SDCA drivers
Date: Thu, 22 May 2025 09:45:27 +0100 [thread overview]
Message-ID: <174790352786.11863.7427900599008667887.b4-ty@kernel.org> (raw)
In-Reply-To: <20250516131011.221310-1-ckeepax@opensource.cirrus.com>
On Fri, 16 May 2025 14:10:04 +0100, Charles Keepax wrote:
> Add helper functions to add DAPM widgets, routes, ALSA controls,
> and DAI drivers, these will be used to create SDCA function device
> drivers.
>
> This series should provide most of the core functionality needed to
> get a device registered and have a working DAPM graph within the
> device. There are some features that still need additional work, these
> are marked with FIXMEs in the code. The two main things are SDCA
> Clock Muxes (not used in our devices and needs some ASoC core work),
> and better support for more complex SDCA volume control definitions
> (our parts have fairly simple volumes, and SDCA has a large amount of
> flexibility in how the volume control is specified).
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: SDCA: Fix minor typo
commit: 52b97d43b7c52da481758931a111a091da5e4802
[2/7] ASoC: SDCA: Remove regmap module macros
commit: 96bd04e738f8154b1d798842e89a4fa8b85d2636
[3/7] ASoC: SDCA: Move allocation of PDE delays array
commit: 3849c958eeeb8e340112b983068c5547babc7274
[4/7] ASoC: dapm: Add component level pin switches
commit: 737379e5062e26c59fe069a8bdad2ee363d52686
[5/7] ASoC: SDCA: Create DAPM widgets and routes from DisCo
commit: 2c8b3a8e6aa877583e5dc2f669a8adc896a771d4
[6/7] ASoC: SDCA: Create ALSA controls from DisCo
commit: c3ca24e3fcb656c6afe702b69e6e9efcc3ff1128
[7/7] ASoC: SDCA: Create DAI drivers from DisCo
commit: 108f878d435437f649da32dea9f0d4f684eba3ba
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2025-05-22 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 13:10 [PATCH v6 0/7] Add DAPM/ASoC helpers to create SDCA drivers Charles Keepax
2025-05-16 13:10 ` [PATCH v6 1/7] ASoC: SDCA: Fix minor typo Charles Keepax
2025-05-16 13:10 ` [PATCH v6 2/7] ASoC: SDCA: Remove regmap module macros Charles Keepax
2025-05-16 13:10 ` [PATCH v6 3/7] ASoC: SDCA: Move allocation of PDE delays array Charles Keepax
2025-05-16 13:10 ` [PATCH v6 4/7] ASoC: dapm: Add component level pin switches Charles Keepax
2025-05-16 13:10 ` [PATCH v6 5/7] ASoC: SDCA: Create DAPM widgets and routes from DisCo Charles Keepax
2025-05-16 13:10 ` [PATCH v6 6/7] ASoC: SDCA: Create ALSA controls " Charles Keepax
2025-05-16 13:10 ` [PATCH v6 7/7] ASoC: SDCA: Create DAI drivers " Charles Keepax
2025-05-19 18:07 ` [PATCH v6 0/7] Add DAPM/ASoC helpers to create SDCA drivers Pierre-Louis Bossart
2025-05-22 8:45 ` Mark Brown [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=174790352786.11863.7427900599008667887.b4-ty@kernel.org \
--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