From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@openedhand.com>
Cc: linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [PATCH 1/6] mfd: Pass driver_data onto child devices
Date: Thu, 18 Dec 2008 10:44:39 +0000 [thread overview]
Message-ID: <1229597084-12727-1-git-send-email-broonie@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20081218104301.GA12649@rakim.wolfsonmicro.main>
The MFD cell structure provides a driver_data field but doesn't pass it
on to the child devices when instantiating them - do that.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
---
drivers/mfd/mfd-core.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c
index 6c0d1be..54ddf37 100644
--- a/drivers/mfd/mfd-core.c
+++ b/drivers/mfd/mfd-core.c
@@ -34,6 +34,7 @@ static int mfd_add_device(struct device *parent, int id,
goto fail_device;
pdev->dev.parent = parent;
+ platform_set_drvdata(pdev, cell->driver_data);
ret = platform_device_add_data(pdev,
cell->platform_data, cell->data_size);
--
1.5.6.5
next prev parent reply other threads:[~2008-12-18 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 10:43 [PATCH 0/6] MFD updates Mark Brown
2008-12-18 10:44 ` Mark Brown [this message]
2008-12-18 10:44 ` [PATCH 2/6] mfd: Register WM8400 codec device Mark Brown
2008-12-18 10:44 ` [PATCH 3/6] mfd: Add WM8352 support Mark Brown
2008-12-18 10:44 ` [PATCH 4/6] mfd: Handle missing WM8350 platform data Mark Brown
2008-12-18 10:44 ` [PATCH 5/6] mfd: Support configurable numbers of DCDCs and ISINKs on WM8350 Mark Brown
2008-12-18 10:44 ` [PATCH 6/6] mfd: Add WM8351 support Mark Brown
2008-12-18 10:58 ` [PATCH 0/6] MFD updates Samuel Ortiz
2008-12-18 11:04 ` Mark Brown
2008-12-18 22:25 ` Samuel Ortiz
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=1229597084-12727-1-git-send-email-broonie@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@openedhand.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
Powered by JetHome