All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 1/2] ASoC: Pay attention to driver	supplied DAI IDs
Date: Tue, 12 Oct 2010 22:33:55 +0100	[thread overview]
Message-ID: <20101012213355.GA14320@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTikNLX_0y4Mo3TqsjAecHk8x0ZR-_iz3EL87vkUM@mail.gmail.com>

On Tue, Oct 12, 2010 at 01:49:52PM -0500, Timur Tabi wrote:
> On Tue, Oct 12, 2010 at 9:57 AM, Mark Brown

> > -               dai->id = i;
> > +               if (dai->driver->id)
> > +                       dai->id = dai->driver->id;
> > +               else
> > +                       dai->id = i;

> I haven't looked at the code, but doesn't this assume that a DAI ID of
> 0 is invalid?

> I have a suspicion I need to retest my driver to make sure it still works.

This makes no change to the behaviour when the DAI ID is zero.
Previously it would be overwritten with i, with the new code it is still
overwritten with i.  You can specify a DAI ID of zero, but only for the
first DAI.  This is a limitation but avoids having to manually set the
DAI ID in the simple case where they're all numbered sequentially from
zero.

      reply	other threads:[~2010-10-12 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 14:57 [PATCH 1/2] ASoC: Pay attention to driver supplied DAI IDs Mark Brown
2010-10-12 14:57 ` [PATCH 2/2] ASoC: Restore DAI ID specification for WM8994 Mark Brown
2010-10-13  9:30   ` Liam Girdwood
2010-10-12 17:05 ` [PATCH 1/2] ASoC: Pay attention to driver supplied DAI IDs Mark Brown
2010-10-12 18:49 ` Timur Tabi
2010-10-12 21:33   ` Mark Brown [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=20101012213355.GA14320@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=timur@freescale.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.