Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	Mengdong Lin <mengdong.lin@intel.com>,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: topology: Update ABI with improvements for TLV, operations and private data.
Date: Wed, 05 Aug 2015 12:43:02 +0100	[thread overview]
Message-ID: <1438774982.16660.32.camel@loki> (raw)
In-Reply-To: <20150805112907.GI20873@sirena.org.uk>

On Wed, 2015-08-05 at 12:29 +0100, Mark Brown wrote:
> On Wed, Aug 05, 2015 at 11:11:07AM +0100, Liam Girdwood wrote:
> > From: Mengdong Lin <mengdong.lin@intel.com>
> > 
> > This is the kernel patch - a corresponding alsa-lib patch has also been sent.
> 
> This patch introduces multiple changes and should really have been sent
> separately.  Please also try to keep your commit messages and especially
> subject lines under 80 colummns so that they are legible.
> 

The concern with multiple patches is that it's more likely to break
runtime bisection/alignment with userspace (but I guess we have that
anyway now), hence the squashing into a single patch for userspace and
kernel.

I'll rework into six patches (three kernel and three userspace).


> > Removed the following fields from topology TLV struct:
> > - size/count: type can decide the size.
> 
> >  struct snd_soc_tplg_ctl_tlv {
> > -	__le32 size;	/* in bytes aligned to 4 */
> > -	__le32 numid;	/* control element numeric identification */
> > -	__le32 count;	/* number of elem in data array */
> > -	__le32 data[SND_SOC_TPLG_TLV_SIZE];
> > +	__le32 size;	/* in bytes of this structure */
> > +	__le32 type;	/* SNDRV_CTL_TLVT_*, type of TLV */
> > +	union {
> > +		struct snd_soc_tplg_tlv_dbscale scale;
> > +	};
> 
> The combination of removing size fromm the struct and not having data
> means that we can't in the future add a new type which has a larger size
> than the current one without confusing older systems (Rather than just
> having them drop the TLV information).  I'm not sure how likely that
> really is but it's a consideration.

Oh, data should have still been in there. Size just had it's comment
fixed to match the other size usage in the other structures.

Liam

      reply	other threads:[~2015-08-05 11:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 10:11 [PATCH] ASoC: topology: Update ABI with improvements for TLV, operations and private data Liam Girdwood
2015-08-05 11:29 ` Mark Brown
2015-08-05 11:43   ` Liam Girdwood [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=1438774982.16660.32.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=mengdong.lin@intel.com \
    --cc=tiwai@suse.de \
    /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