From: Dmitry Osipenko <digetx@gmail.com>
To: Jonathan Hunter <jonathanh@nvidia.com>
Cc: alsa-devel@alsa-project.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.com>,
Jaroslav Kysela <perex@perex.cz>, Ion Agorria <ion@agorria.com>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v6 0/4] Unify NVIDIA Tegra ASoC machine drivers
Date: Mon, 7 Jun 2021 16:43:52 +0300 [thread overview]
Message-ID: <09a8bd07-d816-038c-8722-82bf0f3cc983@gmail.com> (raw)
In-Reply-To: <20210529154649.25936-1-digetx@gmail.com>
29.05.2021 18:46, Dmitry Osipenko пишет:
> This series squashes all the ASoC machine drivers into a single one,
> this change was suggested by Jon Hunter. It also sets driver_name and
> components string of each card, allowing userspace alsa-lib to find
> UCMs at predictable path.
>
> Changelog:
>
> v6: - Fixed missed configuration of AC97 clock rate for the WM9712 codec
> in the unified driver.
>
> - Added new patch that removes now obsolete "utils" helpers and moves
> code into the unified driver.
>
> ASoC: tegra: Squash utils into common machine driver
Jon, please feel free to give yours ack if v6 patches are good to you.
next prev parent reply other threads:[~2021-06-07 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 15:46 [PATCH v6 0/4] Unify NVIDIA Tegra ASoC machine drivers Dmitry Osipenko
2021-05-29 15:46 ` [PATCH v6 1/4] ASoC: tegra: Set driver_name=tegra for all " Dmitry Osipenko
2021-05-29 15:46 ` [PATCH v6 2/4] ASoC: tegra: Unify ASoC " Dmitry Osipenko
2021-05-29 15:46 ` [PATCH v6 3/4] ASoC: tegra: Specify components string for each card Dmitry Osipenko
2021-05-29 15:46 ` [PATCH v6 4/4] ASoC: tegra: Squash utils into common machine driver Dmitry Osipenko
2021-06-07 13:43 ` Dmitry Osipenko [this message]
2021-06-15 12:06 ` [PATCH v6 0/4] Unify NVIDIA Tegra ASoC machine drivers Mark Brown
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=09a8bd07-d816-038c-8722-82bf0f3cc983@gmail.com \
--to=digetx@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=clamor95@gmail.com \
--cc=ion@agorria.com \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=thierry.reding@gmail.com \
--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