linux-kernel - Re: [PATCH v2] pwm: imx-pwm: add explicit compatible strings and required clock properties

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150311084827.GA19577@ulmo.nvidia.com>
Date:	Wed, 11 Mar 2015 09:48:29 +0100
From:	Thierry Reding <thierry.reding@...il.com>
To:	Matt Porter <mporter@...sulko.com>
Cc:	Devicetree List <devicetree@...r.kernel.org>,
	Rob Herring <robh+dt@...nel.org>,
	Mark Rutland <mark.rutland@....com>,
	Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
	Linux PWM List <linux-pwm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] pwm: imx-pwm: add explicit compatible strings and
 required clock properties

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@...sulko.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

Content of type "application/pgp-signature" skipped