devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Matt Porter <mporter@konsulko.com>
Cc: Devicetree List <devicetree@vger.kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
	Linux PWM List <linux-pwm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pwm: imx-pwm: add explicit compatible strings and required clock properties
Date: Sun, 8 Mar 2015 17:09:16 -0500	[thread overview]
Message-ID: <CAL_JsqLWjJN7ar99DZAVLHVfUxek8GyApTSGhmRjGrEDzdtCHQ@mail.gmail.com> (raw)
In-Reply-To: <20150306163721.GL19577@beef>

On Fri, Mar 6, 2015 at 10:37 AM, Matt Porter <mporter@konsulko.com> wrote:
> On Fri, Mar 06, 2015 at 09:16:44AM -0600, Rob Herring wrote:
>> On Fri, Mar 6, 2015 at 9:09 AM, Matt Porter <mporter@konsulko.com> wrote:
>> > The imx-pwm binding contains language indicating compatible
>> > strings to be used that is not valid for all supported parts
>> > e.g. Should be "fsl,<soc>-pwm". Fix this by enumerating the
>> > valid compatible strings that represent the two versions of
>> > this peripheral in use.
>> >
>> > The binding is also missing the clocks/clock-names properties
>> > so document these,the two required ipg and per clocks, and add
>> > add these properties to the example.
>> >
>> > Signed-off-by: Matt Porter <mporter@konsulko.com>
>> > ---
>> >  Documentation/devicetree/bindings/pwm/imx-pwm.txt | 11 ++++++++++-
>> >  1 file changed, 10 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/Documentation/devicetree/bindings/pwm/imx-pwm.txt b/Documentation/devicetree/bindings/pwm/imx-pwm.txt
>> > index b50d7a6d..30d2b82 100644
>> > --- a/Documentation/devicetree/bindings/pwm/imx-pwm.txt
>> > +++ b/Documentation/devicetree/bindings/pwm/imx-pwm.txt
>> > @@ -1,10 +1,16 @@
>> >  Freescale i.MX PWM controller
>> >
>> >  Required properties:
>> > -- compatible: should be "fsl,<soc>-pwm"
>> > +- compatible :
>> > +  - "fsl,imx1-pwm" for PWM compatible with the one integrated on i.MX1
>> > +  - "fsl,imx27-pwm" for PWM compatible with the one integrated on i.MX27
>>
>> This should be one of these and a more specific value as the example
>> below shows.
>
> Ok, yes, I wasn't sure if that was expected to be explicit in the bindings
> or not as others don't seem to represent that properly. What about this?
>
> - compatible: should be "fsl,<soc>-pwm" and one of the following
>               compatible strings:
>                 "fsl,imx1-pwm" for an iMX1 compatible PWM
>                 "fsl,imx27-pwm" for an iMX27 compatible PWM

Looks fine.

Rob

      reply	other threads:[~2015-03-08 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 15:09 [PATCH] pwm: imx-pwm: add explicit compatible strings and required clock properties Matt Porter
2015-03-06 15:16 ` Rob Herring
2015-03-06 16:37   ` Matt Porter
2015-03-08 22:09     ` Rob Herring [this message]

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=CAL_JsqLWjJN7ar99DZAVLHVfUxek8GyApTSGhmRjGrEDzdtCHQ@mail.gmail.com \
    --to=robherring2@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mporter@konsulko.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).