From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Chavan <ashish.chavan@gmail.com>
Cc: alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: Query about regmap SPI
Date: Tue, 6 Mar 2012 12:10:48 +0000 [thread overview]
Message-ID: <20120306121048.GJ19635@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAH4H7mPZtJqwYN=ZMp1N9MP0GM0hZhnW+5z1V2-ZwqYba9jAWQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 710 bytes --]
On Tue, Mar 06, 2012 at 12:53:51PM +0500, Ashish Chavan wrote:
> I am planning to add SPI support for da7210 codec driver. SPI for this
> codec has slightly different format than others. It has 8 bit register
Please always CC the relevant mailing lists on postings. I shouldn't
need to remind you about this stuff.
> Is there any other way to achieve this using regmap? The only other way
> I can think of is providing a wrapper function to read and write in
> codec driver and doing the shifting job inside that wrapper.
No, implementing stuff like this in individual device drivers rather
defeats the point of having frameworks. It sounds like it should be
trivial to add support for this to regmap.
[-- 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-06 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 7:53 Query about regmap SPI Ashish Chavan
2012-03-06 12:10 ` Mark Brown [this message]
[not found] <1331045140.32512.7.camel@matrix>
2012-03-06 15:08 ` Ashish Chavan
2012-03-06 16:30 ` Mark Brown
2012-03-06 17:34 ` Ashish Chavan
2012-03-06 19:59 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2012-03-05 13:20 Query About " 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=20120306121048.GJ19635@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=ashish.chavan@gmail.com \
--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).