From: Mark Brown <broonie@kernel.org>
To: krzk+dt@kernel.org, povik+lin@cutebit.org, tiwai@suse.com,
lgirdwood@gmail.com, perex@perex.cz, robh+dt@kernel.org
Cc: sven@svenpeter.dev, asahi@lists.linux.dev, kettenis@openbsd.org,
marcan@marcan.st, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [RFC PATCH v2 0/5] Apple Macs machine/platform ASoC driver
Date: Fri, 10 Jun 2022 16:58:44 +0100 [thread overview]
Message-ID: <165487672494.1755957.15170830453341675210.b4-ty@kernel.org> (raw)
In-Reply-To: <20220606191910.16580-1-povik+lin@cutebit.org>
On Mon, 6 Jun 2022 21:19:05 +0200, Martin Povišer wrote:
> This is again RFC with a machine-level ASoC driver for recent Apple Macs
> with the M1 line of chips. This time I attached the platform driver too
> for good measure. What I am interested in the most is checking the overall
> approach, especially on two points (both in some ways already discussed
> in previous RFC [0]):
>
> - The way the platform/machine driver handles the fact that multiple I2S
> ports (now backend DAIs) can be driven by/connected to the same SERDES
> unit (now in effect a frontend DAI). After previous discussion I have
> transitioned to DPCM to model this. I took the opportunity of dynamic
> backend/frontend routing to support speakers/headphones runtime
> switching. More on this in comments at top of the machine and platform
> driver.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[4/5] ASoC: Introduce 'fixup_controls' card method
commit: df4d27b19b892f464685ea45fa6132dd1a2b6864
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:[~2022-06-10 15:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 19:19 Martin Povišer
2022-06-06 19:19 ` [RFC PATCH v2 1/5] dt-bindings: sound: Add Apple MCA I2S transceiver Martin Povišer
2022-06-06 19:44 ` Mark Brown
2022-06-09 18:44 ` Rob Herring
2022-06-06 19:19 ` [RFC PATCH v2 2/5] dt-bindings: sound: Add Apple Macs sound peripherals Martin Povišer
2022-06-06 19:49 ` Mark Brown
2022-06-09 20:03 ` Rob Herring
2022-06-06 19:19 ` [RFC PATCH v2 3/5] ASoC: apple: Add MCA platform driver for Apple SoCs Martin Povišer
2022-06-06 20:17 ` Mark Brown
2022-06-06 20:35 ` Martin Povišer
2022-06-06 19:19 ` [RFC PATCH v2 4/5] ASoC: Introduce 'fixup_controls' card method Martin Povišer
2022-06-06 19:19 ` [RFC PATCH v2 5/5] ASoC: apple: Add macaudio machine driver Martin Povišer
2022-06-06 20:02 ` Pierre-Louis Bossart
2022-06-06 20:46 ` Martin Povišer
2022-06-06 21:22 ` Pierre-Louis Bossart
2022-06-06 21:33 ` Martin Povišer
2022-06-09 13:16 ` Mark Brown
2022-06-09 13:42 ` Martin Povišer
2022-06-09 15:03 ` Mark Brown
[not found] ` <2A0422B8-8367-457E-A146-730F7C3DE66B@cutebit.org>
[not found] ` <YqIWtzphzVGmbIOe@sirena.org.uk>
2022-06-09 16:19 ` Martin Povišer
2022-06-09 16:35 ` Mark Brown
2022-06-09 13:33 ` Mark Brown
2022-06-09 14:09 ` Martin Povišer
2022-06-09 15:16 ` Mark Brown
2022-06-09 15:27 ` Martin Povišer
2022-06-09 15:53 ` [RFC PATCH v2 0/5] Apple Macs machine/platform ASoC driver Mark Brown
2022-06-10 15:58 ` 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=165487672494.1755957.15170830453341675210.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=asahi@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=kettenis@openbsd.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=perex@perex.cz \
--cc=povik+lin@cutebit.org \
--cc=robh+dt@kernel.org \
--cc=sven@svenpeter.dev \
--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®