All of lore.kernel.org
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org, Arun KS <arunks@mistralsolutions.com>
Subject: Re: [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec
Date: Mon, 29 Sep 2008 14:15:14 -0700	[thread overview]
Message-ID: <48E14562.5030906@boundarydevices.com> (raw)
In-Reply-To: <20080929195011.GC21010@sirena.org.uk>

> 
> That said, there is an issue with this at the minute due to the fact
> that the core does not yet use the device model properly and
> (essentially) hangs all the drivers off the codec device which leads to
> having both ai23_probe() which registers the I2C driver and
> aic23_codec_probe().  This is half way to being rectified (the code
> exists but is in the process of being merged) so that what happens is
> that all the components of the system register with the ASoC core after
> being probed normally from registrations done in the board init code or
> similar.  This will remove all the socdev interaction from the codec
> driver which is, I think, what you're getting at?

Thanks for the explanation and status update. I have no problem with doing
both in the codec until this code is merged.


Thanks
Troy

  reply	other threads:[~2008-09-29 21:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29  9:41 [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec Arun KS
2008-09-29 16:47 ` Troy Kisky
2008-09-29 16:54   ` Mark Brown
2008-09-29 17:05     ` Troy Kisky
2008-09-29 17:32       ` Mark Brown
2008-09-29 17:27     ` Troy Kisky
2008-09-29 17:39       ` Mark Brown
2008-09-29 17:58         ` Troy Kisky
2008-09-29 18:30           ` Mark Brown
2008-09-29 19:07             ` Troy Kisky
2008-09-29 19:50               ` Mark Brown
2008-09-29 21:15                 ` Troy Kisky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-29  9:41 Arun KS

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=48E14562.5030906@boundarydevices.com \
    --to=troy.kisky@boundarydevices.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arunks@mistralsolutions.com \
    --cc=broonie@sirena.org.uk \
    /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.