From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH 0/3] alsa-lib/ASoC: use inclusive language for bclk/fsync/topology
Date: Tue, 29 Sep 2020 09:18:12 +0200 [thread overview]
Message-ID: <s5hlfgtkq4r.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200918212832.249184-1-pierre-louis.bossart@linux.intel.com>
On Fri, 18 Sep 2020 23:28:29 +0200,
Pierre-Louis Bossart wrote:
>
> The SOF (Sound Open Firmware) tree contains a lot of references in
> topology files to 'codec_slave'/'codec_master' terms, which in turn
> come from alsa-lib and ALSA/ASoC topology support at the kernel
> level. These terms are no longer compatible with the guidelines
> adopted by the kernel community [1] and need to change in
> backwards-compatible ways.
>
> The main/secondary terms typically suggested in guidelines don't mean
> anything for clocks, this patchset suggests instead the use of
> 'provider' and 'consumer' terms, with the 'codec' prefix kept to make
> it clear that the codec is the reference. The CM/CS suffixes are also
> replaced by CP/CC.
>
> It can be argued that the change of suffix is invasive, but finding a
> replacement that keeps the M and S shortcuts has proven difficult in
> quite a few contexts.
>
> The previous definitions are kept for backwards-compatibility so this
> change should not have any functional impact. It is suggested that new
> contributions only use the new terms but there is no requirement to
> transition immediately to the new definitions for existing code. Intel
> will however update all its past contributions related to bit
> clock/frame sync configurations immediately.
>
> This suggestion is easier to review first at the alsa-lib level, and
> if agreed follow-up contributions for the Linux kernel [2] and SOF
> firmware [3] will be provided.
It's OK from alsa-lib POV; although the uapi header change isn't 100%
safe, the user of this header is really our ones, so it's practically
acceptable, I suppose.
Could you submit the changes for kernel, so that it can be merged in
time? Basically alsa-lib is synced with kernel, so the kernel should
be changed at first.
thanks,
Takashi
>
> Feedback welcome
> ~Pierre
>
> [1] https://lkml.org/lkml/2020/7/4/229
> [2] https://github.com/plbossart/sound/tree/fix/inclusive-language-bclk-fsync
> [3] https://github.com/plbossart/sof/tree/fix/inclusive-language-bclk-fsync
>
> Changes since RFC:
> replaced 'follower' by 'consumer' as suggested by Jaroslav and Marc
> minor cleanups
>
> Pierre-Louis Bossart (3):
> topology: use inclusive language for bclk
> topology: use inclusive language for fsync
> topology: use inclusive language in documentation
>
> include/sound/uapi/asoc.h | 22 +++++++-----
> include/topology.h | 8 ++---
> src/topology/pcm.c | 75 +++++++++++++++++++++++++++------------
> 3 files changed, 71 insertions(+), 34 deletions(-)
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2020-09-29 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 21:28 [PATCH 0/3] alsa-lib/ASoC: use inclusive language for bclk/fsync/topology Pierre-Louis Bossart
2020-09-18 21:28 ` [PATCH 1/3] topology: use inclusive language for bclk Pierre-Louis Bossart
2020-09-18 21:28 ` [PATCH 2/3] topology: use inclusive language for fsync Pierre-Louis Bossart
2020-09-18 21:28 ` [PATCH 3/3] topology: use inclusive language in documentation Pierre-Louis Bossart
2020-09-29 7:18 ` Takashi Iwai [this message]
2020-09-29 13:44 ` [PATCH 0/3] alsa-lib/ASoC: use inclusive language for bclk/fsync/topology 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=s5hlfgtkq4r.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@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;
as well as URLs for NNTP newsgroup(s).