From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Sheetal <sheetal@nvidia.com>, Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mohan Kumar <mkumard@nvidia.com>,
linux-sound@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] ASoC: tegra: ASRC control fixes and ratio caching
Date: Mon, 21 Sep 2026 14:51:00 +0200 [thread overview]
Message-ID: <arEoNAC729MT5Bqr@sirena.co.uk> (raw)
In-Reply-To: <arEaioTIrCyJqwKn@orome>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
On Mon, Sep 21, 2026 at 02:07:19PM +0200, Thierry Reding wrote:
> Given the ABI change, do we have a good understanding of who might be
> using these features? My understanding is that these are used for the
> setup of hardware pipelines involving sample rate conversions. So these
> are likely not your regular users that just want to change the volume
> for headphones and such. This is for highly specific use-cases. Do we
> know if people use extra userspace software on top of ALSA to set these
> up, or are they typically dealing with fixed configuration files for
> specifying these values?
...
> Mark, Liam, do you have any guidelines on how to handle such ABI
> changes?
I don't really, beyond your already very good summary. It depends a lot
on knowledge of the users for the device, their level of expertise and
how likely anyone is to be using the individual feature in the first
place. Obviously it's an ABI break so we shouldn't really be doing it
if we can avoid it, but if everyone involved is happy and has a good way
to deal with the changes then it's not really a problem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-09-21 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 8:57 Sheetal
2026-09-21 8:57 ` [RFC PATCH 1/3] ASoC: tegra: Fix ASRC Stream6 input threshold control Sheetal
2026-09-21 11:38 ` Thierry Reding
2026-09-21 8:57 ` [RFC PATCH 2/3] ASoC: tegra: Update ASRC ratio controls Sheetal
2026-09-21 11:50 ` Thierry Reding
2026-09-21 8:57 ` [RFC PATCH 3/3] ASoC: tegra: Cache ASRC ratios until streams are active Sheetal
2026-09-21 12:07 ` [RFC PATCH 0/3] ASoC: tegra: ASRC control fixes and ratio caching Thierry Reding
2026-09-21 12:51 ` 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=arEoNAC729MT5Bqr@sirena.co.uk \
--to=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=sheetal@nvidia.com \
--cc=spujar@nvidia.com \
--cc=thierry.reding@kernel.org \
--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®