From: Andres Salomon <dilinger@queued.net>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [PATCH 0/17] mfd sharing support (v2, part 1)
Date: Fri, 11 Feb 2011 17:57:35 -0800 [thread overview]
Message-ID: <20110211175735.0d4258dc@queued.net> (raw)
Hi,
Here's my second attempt[0] of the MFD sharing. Rather than go
through with the whole thing, this is just the part which makes
mfd_cells always available to MFD clients. I'm planning to later
remove driver_data, and just use a (renamed) platform_data as a
general cleanup, but for now.. Here's the first part.
Again, the goal here is to allow MFD clients to share MFD driver
resources. Each platform device that an MFD driver creates has
the mfd_cell that created it located in its platform_data area. For
drivers that were using the mfd_cell's platform_data field for other
purposes, this is now available by grabbing the mfd_cell and looking at
its platform_data field.
[0] first attempt -
http://thread.gmane.org/gmane.linux.kernel/1095524/focus=1095546
next reply other threads:[~2011-02-12 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 1:57 Andres Salomon [this message]
2011-02-14 16:31 ` [PATCH 0/17] mfd sharing support (v2, part 1) Mark Brown
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=20110211175735.0d4258dc@queued.net \
--to=dilinger@queued.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.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