From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Chavan <ashish.chavan@kpitcummins.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
alsa-devel <alsa-devel@alsa-project.org>, lrg <lrg@ti.com>,
"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH] ASoC: da7210: Add support for spi regmap
Date: Wed, 21 Mar 2012 16:38:12 +0000 [thread overview]
Message-ID: <20120321163811.GH3226@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332348080.21744.26.camel@matrix>
[-- Attachment #1.1: Type: text/plain, Size: 1293 bytes --]
On Wed, Mar 21, 2012 at 10:11:20PM +0530, Ashish Chavan wrote:
> On Wed, 2012-03-21 at 15:56 +0000, Mark Brown wrote:
> This is writing to page register. SPI register space is divided in to
> two pages. Registers from 0x01 to 0x80 fall in to first page. If we want
> to write to any register above 0x80, first we need to set page register
> with PAGE1. May be I should put comments to make it obvious.
You also need to make sure that the register cache doesn't get confused.
> > > /* unlock */
> > > regmap_write(da7210->regmap, DA7210_A_HID_UNLOCK, 0x8B);
> > > @@ -1035,6 +1056,10 @@ static int da7210_probe(struct snd_soc_codec *codec)
> > > regmap_write(da7210->regmap, DA7210_A_HID_UNLOCK, 0x00);
> > > regmap_write(da7210->regmap, DA7210_A_TEST_UNLOCK, 0x00);
> > I also note that you've not yet updated this to use a regmap patch as
> > was previously requested.
> Actually I don't have enough details about the problem that you
> mentioned with this. I am waiting for inputs from some body else. Can
...and didn't bother asking any questions so it's unlikely anyone will
say anything...
> you please elaborate the problem if you have details? so that I can
> correct it.
What is unclear in the previous feedback? You should be converting this
to use a regmap patch...
[-- 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-03-21 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 15:52 [PATCH] ASoC: da7210: Add support for spi regmap Ashish Chavan
2012-03-21 15:56 ` [alsa-devel] " Mark Brown
2012-03-21 16:41 ` Ashish Chavan
2012-03-21 16:38 ` Mark Brown [this message]
2012-03-21 17:05 ` Ashish Chavan
2012-03-21 17:22 ` [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=20120321163811.GH3226@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashish.chavan@kpitcummins.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).