From: Samuel Ortiz <sameo@linux.intel.com>
To: Daniel Drake <dsd@laptop.org>
Cc: Paul Fox <pgf@laptop.org>, Andres Salomon <dilinger@queued.net>,
linux-kernel@vger.kernel.org
Subject: Re: MFD cell structure and sharing of resources
Date: Fri, 24 Dec 2010 11:45:19 +0100 [thread overview]
Message-ID: <20101224104518.GB27832@sortiz-mobl> (raw)
In-Reply-To: <AANLkTi=ypose5day4=ypV8_SsiFq4vf9vqZh-OWret0x@mail.gmail.com>
Hi Daniel,
On Thu, Dec 16, 2010 at 03:38:52PM +0000, Daniel Drake wrote:
> Hi Samuel,
>
> Thanks for your valuable input here!
Thanks for your patience. I've been swamped at work with other projects, sorry
for the delay.
> I have one solution in mind but I'm not sure if it goes beyond your
> definition of what a mfd cell should be:
>
> cs5535-mfd creates and registers a MFD cell specifically for
> olpc-xo1-pm if it finds itself running on an XO laptop. The cell has
> the 2 resources that are needed by that driver, and has name
> "olpc-xo1-pm". Therefore our sysfs paths start with:
> /sys/devices/pci0000:00/0000:00:0f.0/olpc-xo1-pm/
That is stretching things a bit, but I'd be ok with that solution.
In theory, you wouldn't even need to check if you're on an XO laptop, except
for saving a few bytes at runtime.
One more thing: What about my proposal of defining IO routines from the MFD
driver, and using those from your subdevices driver ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2010-12-24 10:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 15:37 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 [this message]
2010-12-25 6:48 ` Andres Salomon
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=20101224104518.GB27832@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgf@laptop.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
Powered by JetHome