From: Thierry Reding <thierry.reding@gmail.com>
To: Matt Porter <mporter@konsulko.com>
Cc: Devicetree List <devicetree@vger.kernel.org>,
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 v2] pwm: imx-pwm: add explicit compatible strings and required clock properties
Date: Wed, 11 Mar 2015 09:48:29 +0100 [thread overview]
Message-ID: <20150311084827.GA19577@ulmo.nvidia.com> (raw)
In-Reply-To: <1425907461-13538-1-git-send-email-mporter@konsulko.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Mon, Mar 09, 2015 at 09:24:21AM -0400, Matt Porter 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>
> ---
> Changes since v1:
> - compatible strings include the actual soc and one of the two specific
> compatible parts.
>
> Documentation/devicetree/bindings/pwm/imx-pwm.txt | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
Applied, thanks.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-11 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 13:24 [PATCH v2] pwm: imx-pwm: add explicit compatible strings and required clock properties Matt Porter
2015-03-09 13:49 ` Rob Herring
2015-03-11 8:48 ` Thierry Reding [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=20150311084827.GA19577@ulmo.nvidia.com \
--to=thierry.reding@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.