From: Mark Brown <broonie@kernel.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, eddie.huang@mediatek.com,
Lee Jones <lee.jones@linaro.org>
Subject: Re: Recommendations for a new MFD device driver?
Date: Fri, 6 Feb 2015 11:54:18 +0000 [thread overview]
Message-ID: <20150206115418.GV21293@sirena.org.uk> (raw)
In-Reply-To: <20150206101006.GK12209@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Fri, Feb 06, 2015 at 11:10:06AM +0100, Sascha Hauer wrote:
> 1) Put it into the RTC device driver.
> 2) Put it into the .resource field of struct mfd_cell
> 3) Put it into the device tree using standard reg, interrupt properties and
> a) Let the RTC driver interpret these
> b) Let the MFD driver create resources in the .resource field of struct
> mfd_cell
> c) Let the MFD core create the resources
> I have a tendency to 3, but I'm afraid that the resource informations
> are duplicated too much in the device tree source files, because every
> user would have to carry a full description of the mfd device. Maybe
> that duplication could be reduced with some CPP magic, I don't know.
> Maybe this is a solved problem and I'm just not picking a good example
> from drivers/mfd.
The wm831x drivers take option 2 but are pre-DT, it still seems the most
sensible thing to me though - no need for the user to have to repeat
this information in every DT and easy to add new stuff if we need it.
You could use a .dtsi like we use for SoCs to reduce the duplication
required if you do decide to put things in the DT.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-02-06 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 10:10 Recommendations for a new MFD device driver? Sascha Hauer
2015-02-06 11:54 ` Mark Brown [this message]
2015-02-06 12:55 ` Yingjoe Chen
2015-02-06 13:52 ` Mark Brown
2015-02-10 7:20 ` Lee Jones
2015-02-11 9:42 ` Sascha Hauer
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=20150206115418.GV21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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