From: Andres Salomon <dilinger@queued.net>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Daniel Drake <dsd@laptop.org>, Paul Fox <pgf@laptop.org>,
linux-kernel@vger.kernel.org
Subject: Re: MFD cell structure and sharing of resources
Date: Fri, 24 Dec 2010 22:48:51 -0800 [thread overview]
Message-ID: <20101224224851.61942d75@queued.net> (raw)
In-Reply-To: <20101224104518.GB27832@sortiz-mobl>
On Fri, 24 Dec 2010 11:45:19 +0100
Samuel Ortiz <sameo@linux.intel.com> wrote:
[...]
>
> One more thing: What about my proposal of defining IO routines from
> the MFD driver, and using those from your subdevices driver ?
>
>
Having looked at the twl4030 driver, I do like that approach. Is this
something you want to see for cs5535 only, or are enough other mfd
drivers doing this that you'd like the mfd framework itself to define
hooks for cell/resource sharing?
next prev parent reply other threads:[~2010-12-25 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 15:37 MFD cell structure and sharing of resources Daniel Drake
2010-12-10 16:34 ` Daniel Drake
2010-12-16 10:35 ` Samuel Ortiz
2010-12-16 15:38 ` Daniel Drake
2010-12-24 10:45 ` Samuel Ortiz
2010-12-25 6:48 ` Andres Salomon [this message]
2010-12-25 14:23 ` Mark Brown
2010-12-24 23:56 ` Andres Salomon
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=20101224224851.61942d75@queued.net \
--to=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgf@laptop.org \
--cc=sameo@linux.intel.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