[RFC PATCH 1/3] topology: use inclusive language for bclk
Pierre-Louis Bossart
pierre-louis.bossart at linux.intel.com
Tue Sep 8 16:41:34 CEST 2020
On 9/8/20 9:35 AM, Mark Brown wrote:
> On Tue, Sep 08, 2020 at 08:39:13AM -0500, Pierre-Louis Bossart wrote:
>
>>>> - __u8 bclk_master; /* SND_SOC_TPLG_BCLK_ value */
>>>> + __u8 bclk_provider; /* SND_SOC_TPLG_BCLK_ value */
>
>>> Is it 100% compatible? Note that the uapi/* header is a copy from the
>>> kernel header, and it means that we'll change the same for the kernel,
>>> too.
>
>> It's absolutely 100% compatible by design.
>> I was planning to update the kernel uapi header to align changes, but the
>> volume of code is much lower on the alsa-lib side. Will resubmit with the
>> preferred provider/consumer wording.
>
> It's binary compatible but it'd break the build for any existing code
> using the UAPI headers.
Sorry, I don't fully get the comment. Aren't the uapi headers copied
into each software tree that relies on them?
More information about the Alsa-devel
mailing list