From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
linux-kernel <linux-kernel@vger.kernel.org>, lrg <lrg@ti.com>
Subject: Re: Query about regmap SPI
Date: Tue, 6 Mar 2012 23:04:12 +0530 [thread overview]
Message-ID: <1331055252.2453.8.camel@matrix> (raw)
In-Reply-To: <20120306163012.GW19635@opensource.wolfsonmicro.com>
On Tue, 2012-03-06 at 16:30 +0000, Mark Brown wrote:
> On Tue, Mar 06, 2012 at 08:38:52PM +0530, Ashish Chavan wrote:
>
> > I also think that there should be a way to handle this kind of stuff by
> > the framework. May I know if you have any plan to add this to regmap? or
> > should I come up with a patch to extend regmap to support this and
> > propose you?
>
> I have no need for it so I'm unlikely to work on it myself, if you were
> to send a patch that'd be great.
OK, I will go through regmap sources in detail to find out appropriate
place to put this. BTW do you have any recommendation in terms of a good
way to achieve this. e.g. will it be useful and generic enough if we
introduce two more fields like read/write_flag_mask to indicate shifting
and use those fields before applying read/write_flag_masks?
next prev parent reply other threads:[~2012-03-06 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1331045140.32512.7.camel@matrix>
2012-03-06 15:08 ` Query about regmap SPI Ashish Chavan
2012-03-06 16:30 ` Mark Brown
2012-03-06 17:34 ` Ashish Chavan [this message]
2012-03-06 19:59 ` Mark Brown
2012-03-06 7:53 Ashish Chavan
2012-03-06 12:10 ` 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=1331055252.2453.8.camel@matrix \
--to=ashish.chavan@kpitcummins.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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).