From: Mark Brown <broonie@kernel.org>
To: Gyungoh Yoo <gyungoh@gmail.com>
Cc: lgirdwood@gmail.com, grant.likely@linaro.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Gyungoh Yoo <jack.yoo@skyworksinc.com>
Subject: Re: [PATCH v2.2 2/2] dt-bindings: Adding compatible attribute for SKY81452 regulator
Date: Mon, 15 Sep 2014 15:35:54 -0700 [thread overview]
Message-ID: <20140915223554.GF7960@sirena.org.uk> (raw)
In-Reply-To: <20140911052230.GA3764@jack-ThinkPad-T520>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Thu, Sep 11, 2014 at 02:22:30PM +0900, Gyungoh Yoo wrote:
> By the way,
> I knew that compatible string is used for binding a driver.
> http://devicetree.org/Device_Tree_Usage#Understanding_the_compatible_Property
> And, from kernel 3.6, MFD core has a mechanism for binding of_node
> to the driver with of_compatible.
> Can I have a question about if it is possible to assign compatible string
> for binding driver independently with reusability?
Look at a driver like the wm831x regulator drivers - they don't have
device tree but they're reusing a driver for an IP with the base
register for the IP being specified in the MFD. If convering to DT it
might be reasonable to specify this in device tree, though it's marginal
since the part name in the core is also good enough.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-15 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 9:10 [PATCH 2/3] Adding Skyworks SKY81452 regulator driver Gyungoh Yoo
2014-08-13 19:04 ` Mark Brown
2014-09-01 2:40 ` [PATCH v2.2 0/2] regulator: sky81452: Adding compatible attribute in DT document Gyungoh Yoo
2014-09-01 2:40 ` [PATCH v2.2 1/2] regulator: sky81452: Adding compatible attribute in DT Gyungoh Yoo
2014-09-01 2:40 ` [PATCH v2.2 2/2] dt-bindings: Adding compatible attribute for SKY81452 regulator Gyungoh Yoo
2014-09-01 10:31 ` Mark Brown
2014-09-05 1:55 ` Gyungoh Yoo
2014-09-06 14:38 ` Mark Brown
2014-09-11 5:22 ` Gyungoh Yoo
2014-09-15 22:35 ` Mark Brown [this message]
2014-09-19 6:17 ` Gyungoh Yoo
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=20140915223554.GF7960@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gyungoh@gmail.com \
--cc=jack.yoo@skyworksinc.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).