From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
hardik.t.shah@intel.com, guneshwor.o.singh@intel.com,
liam.r.girdwood@linux.intel.com, vinod.koul@intel.com,
mengdong.lin@intel.com
Subject: Re: [PATCH 1/5] topology: ABI - Add the types for BE DAI
Date: Sat, 8 Oct 2016 16:00:50 +0800 [thread overview]
Message-ID: <57F8A7B2.2010203@linux.intel.com> (raw)
In-Reply-To: <20161006143731.53vyuwhyyca3vdbm@sirena.org.uk>
On 10/06/2016 10:37 PM, Mark Brown wrote:
> On Mon, Oct 03, 2016 at 11:03:50PM +0800, mengdong.lin@linux.intel.com wrote:
>
>> Pump the version number to 5.
>
> So, we just had a user on IRC complaining that the last round of
> incompatible changes in v4.7 broke their laptop audio - they had a
> laptop that shipped with Linux and suddenly the topology file didn't
> work. I think that's an indication that at this point we have an ABI we
> need to maintain compatibility with rather than just break things. That
> doesn't explicitly affect this patch but does mean that the parsing code
> ought to cope which is likely to have some impact here.
>
>> Topology kernel driver will check size of ABI objects to detect version
>> mismatch between user space and kernel.
>
> The ABI wasn't explicitly reved which suggests that it's this that
> triggered the issue for the user.
Yes. Now if the kernel finds a mismatch of ABI object size, it will just
return error and so old version of topology files cannot work. We'll try
to support ABI version 4 and new versions in kernel. It seems topology
have real users from version 4.
>
>> +/* BE DAI flags */
>> +#define SND_SOC_TPLG_DAI_FLGBIT_SYMMETRIC_RATES (1 << 0)
>> +#define SND_SOC_TPLG_DAI_FLGBIT_SYMMETRIC_CHANNELS (1 << 1)
>> +#define SND_SOC_TPLG_DAI_FLGBIT_SYMMETRIC_SAMPLEBITS (1 << 2)
>
> These don't seem specific to back ends, people can use topologies for
> DSPs on off-SoC devices which might also want to use these.
Yes. Can we take them as generic flags for DAI and DAI links?
>
>> + __le32 be_dai_elems; /* number of BE DAI elements */
>> + __le32 reserved[20]; /* reserved for new ABI element types */
>
> Thinking about the above I'm wondering if it doesn't make more sense to
> call these physical links rather than back ends - that term is going to
> be clearer to people who don't use DPCM.
>
May we call it a "phy_dai_elems", to indicate physical DAIs?
Now the ABI struct "snd_soc_tplg_be_dai" is already in kernel but no
real users in user space. Can we rename it? Or add a new ABI struct?
Thanks
Mengdong
next prev parent reply other threads:[~2016-10-08 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 15:02 [PATCH 0/5] topology: Upgrade ABI to match kernel v4.8 mengdong.lin
2016-10-03 15:03 ` [PATCH 1/5] topology: ABI - Add the types for BE DAI mengdong.lin
2016-10-06 14:37 ` Mark Brown
2016-10-08 8:00 ` Mengdong Lin [this message]
2016-10-11 6:45 ` Mengdong Lin
2016-10-03 15:04 ` [PATCH 2/5] topology: Parse BE DAIs in text conf file mengdong.lin
2016-10-03 15:04 ` [PATCH 3/5] topology: Support configuring BE DAIs by C API mengdong.lin
2016-10-03 15:04 ` [PATCH 4/5] topology: Export BE DAIs to the binary for kernel mengdong.lin
2016-10-03 15:04 ` [PATCH 5/5] topology: ABI - Add sig_bits to stream caps mengdong.lin
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=57F8A7B2.2010203@linux.intel.com \
--to=mengdong.lin@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guneshwor.o.singh@intel.com \
--cc=hardik.t.shah@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@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).