[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141017142605.GU1820@sirena.org.uk>
Date: Fri, 17 Oct 2014 16:26:05 +0200
From: Mark Brown <broonie@...nel.org>
To: Gyungoh Yoo <gyungoh@...il.com>
Cc: sameo@...ux.intel.com, lee.jones@...aro.org, jg1.han@...sung.com,
cooloney@...il.com, lgirdwood@...il.com, jack.yoo@...worksinc.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
grant.likely@...aro.org, robh+dt@...nel.org, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
pawel.moll@....com, heiko@...ech.de, jason@...edaemon.net,
shawn.guo@...escale.com, treding@...dia.com,
florian.vaussard@...l.ch, trivial@...nel.org, linux@...ck-us.net,
andrew@...n.ch, jic23@...nel.org
Subject: Re: [RESUBMIT PATCH v4 7/8] regulator: sky81452: Add compatible
string for device binding
On Fri, Oct 17, 2014 at 07:43:09PM +0900, Gyungoh Yoo wrote:
> Are you talking about simplification using of_regulator_match()?
> This driver has only one regulator.
> Is the API also useful for this driver?
The thing I'm seeing is that the binding for your device with the
subnode looks very much like the device trees of devices with multiple
regulators. The fact that you only have one regulator is a bit
difference but not that much. It seems like drivers should fit into one
of two patterns: either the regulator is described in the root node for
the device for single purpose devices or there should be a collection of
regulators like is supported with this helper API. Having a collection
with only one node doesn't seem to be a problem in any way.
> Like reg-fixed-voltage, how about using of_get_fixed_voltage_config()?
The driver doesn't seem to need any property parsing of its own so it
shoudn't need anything beyond basic calls into the core.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists