All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: MR Swami Reddy <MR.Swami.Reddy@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Deshpande A, Vishwas" <Vishwas.A.Deshpande@ti.com>,
	"Girdwood, Liam" <lrg@ti.com>
Subject: Re: [PATCH RESEND] ASoC: Support TI Isabelle Audio driver
Date: Fri, 1 Jun 2012 13:46:25 +0100	[thread overview]
Message-ID: <20120601124624.GM24139@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FC8B476.4030305@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]

On Fri, Jun 01, 2012 at 05:54:22PM +0530, MR Swami Reddy wrote:
> On Wednesday 30 May 2012 10:10 PM, Mark Brown wrote:

> > If this is all you need then you should be able to use the newly
> > introduced dev_get_regmap() to get the regmap back (other drivers should
> > be being updated for this soon).

> The dev_get_regmap() is not found in the 'for-next' or '3.5' branch. So
> this api can't be used with 'for-next' source base. Please advice. 

It's in Linus' tree so it'll be in for-3.6 just as soon as the merge
window is open.  While the merge window is still open we don't update
anything in for-next except for bug fixes but once the merge window
closes I'll rebase for-3.6 onto -rc1 and add that into for-next.

> > This should really include a list of part numbers - the general
> > expecation people have is that they can just register the part number.

> This audio codec has been referred as 'isabelle' in datasheet and no
> specific part number.

OK, no problem - that's just a bit unusual.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-06-01 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 11:09 [PATCH RESEND] ASoC: Support TI Isabelle Audio driver MR.Swami.Reddy
2012-05-30 16:40 ` Mark Brown
2012-06-01 12:24   ` MR Swami Reddy
2012-06-01 12:46     ` Mark Brown [this message]
2012-06-01 13:52       ` MR Swami Reddy
2012-06-01 13:55         ` 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=20120601124624.GM24139@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=MR.Swami.Reddy@ti.com \
    --cc=Vishwas.A.Deshpande@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.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.