All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: mengdong.lin@intel.com, alsa-devel@alsa-project.org,
	liam.r.girdwood@intel.com
Subject: Re: [PATCH v2 09/10] ASoC: topology: Change stream formats to bitwise flag
Date: Sat, 15 Aug 2015 09:37:34 +0200	[thread overview]
Message-ID: <s5ha8ttypc1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20150814203428.GR10748@sirena.org.uk>

On Fri, 14 Aug 2015 22:34:28 +0200,
Mark Brown wrote:
> 
> On Mon, Aug 10, 2015 at 10:48:37PM +0800, mengdong.lin@intel.com wrote:
> 
> >  struct snd_soc_tplg_stream_caps {
> >  	__le32 size;		/* in bytes of this structure */
> >  	char name[SNDRV_CTL_ELEM_ID_NAME_MAXLEN];
> > -	__le64 formats[SND_SOC_TPLG_MAX_FORMATS];	/* supported formats SNDRV_PCM_FMTBIT_* */
> > +	__le64 formats;	/* supported formats SNDRV_PCM_FORMAT_* */
> 
> Argh, this is *another* ABI change which you've buried in the middle of
> a series you're sending right at the end of the release cycle (this was
> sent after -rc6, we may not even get a -rc7...).  Given how close we are
> to the release and the invasiveness of the changes in this series it's
> very lucky I even saw it before release, I'm reading this on my flight
> to Plumbers which means my bandwidth next week will be limited.

Thanks for checking this.  Mengdong, if there is a change in uapi/*,
this means touching ABI.  So, this change isn't acceptable once when
the kernel is released.  At least, the backward compatibility *must*
be kept no matter which version is.

Also, the patch (and even the current code) looks wrong.  The current
formats[] would receive SNDRV_PCM_FORMAT_* while the comment shows
SNDRV_PCM_FMT_BIT_*.  And your patch changes it again wrongly in the
comment.  Quite confusing.

> This should have at the very least been sent at the start of the series,
> and really should have been sent separately.  It is also worrying that
> there is nothing in the subject or changelog talking about the fact that
> this is an ABI change or explaining why it is required.  The changelog
> was simply a statement of the content of the diff, not a rationale:
> 
> | The toplogy user space tool will generate this bitwise flag by using
> | SNDRV_PCM_FORMAT_* exposed by asound.h, and the topology core will copy
> | this flag when generating DAI streams.
> 
> Once the release goes out this sort of incompatible change will be
> unacceptable.  Given the number of changes that are going into the ABI
> (we also had some others went in last week) I'm now giving some serious
> thought to the idea that we should ask Linus to revert the topology code
> for v4.2 and waiting for v4.3 so we've got more chance to make sure the
> ABI is one we actually want to stick with.  Liam, Takashi I don't know
> what you think?

We can make the topology stuff disabled in Makefile (and the only call
in soc-core.c) instead of the whole revert.  This will be the minimal
impact and safe enough.

BTW, I wonder why there is no Kconfig for topology stuff.  If we had
it, it would have been easy to disable.


thanks,

Takashi

  reply	other threads:[~2015-08-15  7:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 14:45 [PATCH v2 00/10] ASoC: support adding PCM dynamically from topology mengdong.lin
2015-08-10 14:45 ` [PATCH v2 01/10] ASoC: Change the PCM runtime array to a list mengdong.lin
2015-08-14 20:02   ` Mark Brown
2015-08-17  6:28     ` Lin, Mengdong
2015-08-10 14:46 ` [PATCH v2 02/10] ASoC: Define soc_init_dai_link() to wrap link intialization mengdong.lin
2015-08-10 14:47 ` [PATCH v2 03/10] ASoC: Change 2nd argument of soc_bind_dai_link() to DAI link pointer mengdong.lin
2015-08-10 14:47 ` [PATCH v2 04/10] ASoC: Implement DAI links in a list mengdong.lin
2015-08-10 14:47 ` [PATCH v2 05/10] ASoC: Add support for dummy DAI links and PCM runtimes mengdong.lin
2015-08-14 20:22   ` Mark Brown
2015-08-17 10:01     ` Lin, Mengdong
2015-08-17 18:39       ` Mark Brown
2015-08-10 14:48 ` [PATCH v2 06/10] ASoC: Bind new DAI links after probing components mengdong.lin
2015-08-10 14:48 ` [PATCH v2 07/10] ASoC: Support adding a DAI dynamically mengdong.lin
2015-08-10 14:48 ` [PATCH v2 08/10] ASoC: topology: Change pass number of DAI smaller than graph mengdong.lin
2015-08-10 14:48 ` [PATCH v2 09/10] ASoC: topology: Change stream formats to bitwise flag mengdong.lin
2015-08-14 20:34   ` Mark Brown
2015-08-15  7:37     ` Takashi Iwai [this message]
2015-08-15 13:49       ` Lin, Mengdong
2015-08-15 14:45         ` Takashi Iwai
2015-08-15 15:25           ` Lin, Mengdong
2015-08-15 16:50             ` Takashi Iwai
2015-08-15 16:51             ` Mark Brown
2015-08-17 10:05               ` Lin, Mengdong
2015-08-15 15:14         ` Mark Brown
2015-08-15 14:59       ` Mark Brown
2015-08-15 16:52         ` Takashi Iwai
2015-08-10 14:48 ` [PATCH v2 10/10] ASOC: topology: Add PCM DAIs dynamically when loading them mengdong.lin
2015-08-15  7:56 ` [PATCH v2 00/10] ASoC: support adding PCM dynamically from topology Lars-Peter Clausen
2015-08-15 15:50   ` Mark Brown
2015-08-17  6:13     ` Lin, Mengdong
2015-08-17 10:39       ` Liam Girdwood
2015-08-17 20:05         ` Mark Brown
2015-08-18  5:17           ` Lin, Mengdong
2015-08-18  5:27             ` 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=s5ha8ttypc1.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@intel.com \
    --cc=mengdong.lin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.