All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	David@alsa-project.org, Chen <david.chen@diasemi.com>,
	lrg <lrg@ti.com>
Subject: Re: [PATCH v3] ASoC: da7210: Add support for PLL and SRM
Date: Thu, 9 Feb 2012 18:12:20 +0530	[thread overview]
Message-ID: <1328791340.22077.3.camel@matrix> (raw)
In-Reply-To: <20120207191943.GB15929@opensource.wolfsonmicro.com>


> The most common case is things like bluetooth SCO connections where if
> there's a baseband you want to clock from the baseband but if there's no
> baseband (eg, for VoIP calls) you can't do that.  Some devices also need
> to change audio interface configuration depening on things like the
> number of channels.
> 
> Even without any dynamic reconfiguration you also have cases where the
> sequence people use to power things up is to set the clocking and then
> configure the audio interface format - even if the audio interface
> format is always the same you'll still get it being reconfigured the
> first time you start up.

I see.

BTW I am also planning to add SPI support to this driver. Just want to
know if it should be done via reg-map APIs? If yes, then do I need to
convert existing I2C stuff too to use reg-map?

TIA!

  reply	other threads:[~2012-02-09 12:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 11:25 [PATCH v3] ASoC: da7210: Add support for PLL and SRM Ashish Chavan
2012-02-01 11:50 ` Mark Brown
2012-02-01 11:50   ` [alsa-devel] " Mark Brown
2012-02-07 13:25   ` Ashish Chavan
2012-02-07 19:19     ` Mark Brown
2012-02-07 19:19       ` [alsa-devel] " Mark Brown
2012-02-09 12:42       ` Ashish Chavan [this message]
2012-02-09 12:50         ` Mark Brown
2012-02-09 12:50           ` [alsa-devel] " 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=1328791340.22077.3.camel@matrix \
    --to=ashish.chavan@kpitcummins.com \
    --cc=David@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=david.chen@diasemi.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.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.