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 2/8] ASoC: da7210: Add support for DAPM
Date: Thu, 20 Oct 2011 17:17:45 +0530 [thread overview]
Message-ID: <1319111265.24621.14.camel@matrix> (raw)
In-Reply-To: <20111019121341.GE3107@opensource.wolfsonmicro.com>
On Wed, 2011-10-19 at 13:13 +0100, Mark Brown wrote:
> On Wed, Oct 19, 2011 at 12:51:35PM +0530, Ashish Chavan wrote:
>
> > BTW if in case, hardware designers reiterate to use STANDBY registers,
> > will it suffice to only document this somewhere is the source?
>
> The main thing is to make sure that the code is understandable and
> doesn't look buggy to visual inspection so yes, if there's adequate
> documentation that would be OK.
>
I see.
BTW today I received response from hardware designers and as expected,
they are recommending usage of STANDBY registers instead of
ENABLE/DISABLE registers. The main reason for this is that STANDBY
registers are part of system controller which allows system power
up/down in a controlled, pop free manner. Also, as per application note,
STANDBY register bits are only effective if a particular IO (or ADC/DAC)
is already enabled using enable/disable register bits. This is inline
with my previous patch to support DAPM, i.e.
- All IOs and ADC/DAC are enabled using enable/disable register bits in
probe()
- STANDBY mode of all IOs and ADC/DAC is controlled by DAPM
I am thinking of re-posting the patch after adding above info somewhere.
Is there anything else that I need to take care of?
next prev parent reply other threads:[~2011-10-20 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 11:01 [PATCH v3 2/8] ASoC: da7210: Add support for DAPM Ashish Chavan
2011-10-14 19:20 ` Mark Brown
2011-10-15 8:20 ` Ashish Chavan
2011-10-17 21:41 ` Mark Brown
2011-10-19 7:21 ` Ashish Chavan
2011-10-19 12:13 ` Mark Brown
2011-10-20 11:47 ` Ashish Chavan [this message]
2011-10-20 12:36 ` [alsa-devel] " Mark Brown
2011-10-20 13:49 ` Ashish Chavan
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=1319111265.24621.14.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).