[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210114165226.GH4854@sirena.org.uk>
Date: Thu, 14 Jan 2021 16:52:26 +0000
From: Mark Brown <broonie@...nel.org>
To: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@...el.com>
Cc: ulf.hansson@...aro.org, lgirdwood@...il.com, robh+dt@...nel.org,
devicetree@...r.kernel.org, adrian.hunter@...el.com,
michal.simek@...inx.com, linux-mmc@...r.kernel.org,
linux-kernel@...r.kernel.org, andriy.shevchenko@...el.com,
Rashmi.A@...el.com, mahesh.r.vaidya@...el.com
Subject: Re: [PATCH v1 7/9] dt-bindings: regulator: keembay: Add DT binding
documentation
On Thu, Jan 14, 2021 at 11:26:58PM +0800, Muhammad Husaini Zulkifli wrote:
> Add DT Binding Documentation for Keem Bay SD Regulator.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
> +properties:
> + compatible:
> + const: regulator-keembay-sd
Device tree compatible strings should be in the format vendor,device.
> +required:
> + - compatible
> + - regulator-name
Why is regulator-name required here? This is a standard regulator
binding property which is covered by the generic regulator bindings and
should be optional since it is for use by the system integrator to
provide more user friendly diagnostic information about which supply
this is in the system. If you are attempting to use this for device
identification then you should be using different compatible strings for
the different regulators - even if you were using regulator-name you'd
need to document the values.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists