From: Vitaly Andrianov <vitalya@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: using the same regmap by multiple device drivers
Date: Wed, 29 Jun 2016 14:37:47 -0400 [thread overview]
Message-ID: <5774157B.6020609@ti.com> (raw)
In-Reply-To: <20160629183159.GO6247@sirena.org.uk>
On 06/29/2016 02:31 PM, Mark Brown wrote:
> On Wed, Jun 29, 2016 at 01:19:37PM -0400, Vitaly Andrianov wrote:
>
>> Here is my question. Is that actually possible to use in regmap framework
>> the same registers in multiple different drivers?
>
> Of course, this is how the vast majority of MFDs work. The regmap has
> no idea what's calling it, it can't tell if a call comes from one driver
> or another.
>
Thank you.
prev parent reply other threads:[~2016-06-29 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 17:19 using the same regmap by multiple device drivers Vitaly Andrianov
2016-06-29 18:31 ` Mark Brown
2016-06-29 18:37 ` Vitaly Andrianov [this message]
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=5774157B.6020609@ti.com \
--to=vitalya@ti.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
/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).