From: Mark Brown <broonie@kernel.org>
To: "Opensource [Anthony Olech]" <anthony.olech.opensource@diasemi.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [NEW DRIVER V4 0/7] DA9058 PMIC - please comment on this new driver
Date: Tue, 16 Apr 2013 11:20:38 +0100 [thread overview]
Message-ID: <20130416102038.GB26958@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <24DF37198A1E704D9811D8F72B87EB514191E2DC@NB-EX-MBX02.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
On Tue, Apr 16, 2013 at 09:18:41AM +0000, Opensource [Anthony Olech] wrote:
> The reason why they are separate is that they are probed with different data
> structures and they use a different wrapper to access the "regmap" API.
> However, that is not a blocking issue, but it would mean re-writing the core
> MFD component of all the affected drivers. Maybe the way forward is:
> Is it possible to provide some "core" ONKEY API or functionality to handle the
> commonality in a similar fashion to the regulator core as done by Mark Brown?
Well, it's clearly possible to at least turn the polling and interrupt
combination into a library...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-04-16 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 13:05 [NEW DRIVER V4 0/7] DA9058 PMIC - please comment on this new driver Anthony Olech
2013-04-12 18:07 ` Dmitry Torokhov
2013-04-16 9:18 ` Opensource [Anthony Olech]
2013-04-16 10:20 ` Mark Brown [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=20130416102038.GB26958@opensource.wolfsonmicro.com \
--to=broonie@kernel.org \
--cc=anthony.olech.opensource@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=dmitry.torokhov@gmail.com \
--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