From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de,
Javier Martin <javier.martin@vista-silicon.com>,
w.sang@pengutronix.de, lrg@ti.com
Subject: Re: [PATCH v2 2/2] ASoC: tlv320aic32x4: Add rstn gpio to platform data.
Date: Thu, 1 Nov 2012 14:35:15 +0000 [thread overview]
Message-ID: <20121101143514.GJ4413@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50913851.6060003@topic.nl>
[-- Attachment #1.1: Type: text/plain, Size: 653 bytes --]
On Wed, Oct 31, 2012 at 03:40:17PM +0100, Mike Looijmans wrote:
> is a very nice power saving feature. I just cache all the register
> settings up until that point (which required a bit of coding because
> of the "paging" of the I2C address space).
Probably easiest to just convert over to regmap, it handles paging fine.
> It was the best I could think off at the time, and it made me wonder
> why those reset lines aren't modelled this way more often.
This breaks down if any of the drivers actually uses the reset pin to
reset the chip - if the reset might not actually happen but the driver
wants it to happen then things are going to go wrong.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-11-01 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 10:53 [PATCH v2 1/2] ASoC: tlv320aic32x4: Fix problem with first capture Javier Martin
2012-10-31 10:53 ` [PATCH v2 2/2] ASoC: tlv320aic32x4: Add rstn gpio to platform data Javier Martin
2012-10-31 14:40 ` Mike Looijmans
2012-11-01 14:35 ` Mark Brown [this message]
2012-11-01 15:28 ` Mike Looijmans
2012-11-02 14:40 ` Mark Brown
2012-11-05 8:14 ` javier Martin
2012-11-05 8:15 ` Mark Brown
2012-11-01 14:36 ` [PATCH v2 1/2] ASoC: tlv320aic32x4: Fix problem with first capture 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=20121101143514.GJ4413@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=javier.martin@vista-silicon.com \
--cc=lars@metafoo.de \
--cc=lrg@ti.com \
--cc=mike.looijmans@topic.nl \
--cc=w.sang@pengutronix.de \
/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.