From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jonghwa Lee <jonghwa3.lee@samsung.com>,
linux-kernel@vger.kernel.org,
Mike Turquette <mturquette@linaro.org>,
H Hartley Sweeten <hsweetn@visionengravers.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH] clock: max77686: Add driver for Maxim 77686 32KHz crystal oscillator
Date: Sat, 2 Jun 2012 02:50:21 +0000 [thread overview]
Message-ID: <201206020250.21967.arnd@arndb.de> (raw)
In-Reply-To: <20120601162118.GA24139@opensource.wolfsonmicro.com>
On Friday 01 June 2012, Mark Brown wrote:
> On Fri, Jun 01, 2012 at 04:13:33PM +0000, Arnd Bergmann wrote:
>
> > You should also have an of_device_id table so you can match this driver from
> > device tree definitions.
>
> There has been... some discussion on the value of doing this for MFD
> cells where the MFD cell has no reuse capability (eg, when the driver
> has very little abstraction from the top level chip binding) since we
> don't really get anything from the abstraction if the driver can't be
> reused and may limit ourselves (and others) in future.
Ok, makes sense.
Arnd
next prev parent reply other threads:[~2012-06-02 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 9:08 [PATCH] clock: max77686: Add driver for Maxim 77686 32KHz crystal oscillator Jonghwa Lee
2012-06-01 16:13 ` Arnd Bergmann
2012-06-01 16:21 ` Mark Brown
2012-06-02 2:50 ` Arnd Bergmann [this message]
2012-06-11 5:05 ` jonghwa3.lee
-- strict thread matches above, loose matches on Subject: below --
2012-08-28 8:54 [PATCH] clock: max77686: Add driver for Maxim 77686 32Khz " Jonghwa Lee
2012-09-07 0:04 ` Mike Turquette
2012-09-10 1:54 ` jonghwa3.lee
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=201206020250.21967.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=hsweetn@visionengravers.com \
--cc=jonghwa3.lee@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=myungjoo.ham@samsung.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