From: "Sylvain Lemieux" <slemieux.tyco-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: 'Vladimir Zapolskiy' <vz-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [RESEND PATCH] ARM: dts: lpc32xx: set default parent clock for pwm1 & pwm2
Date: Thu, 8 Sep 2016 13:31:48 -0400 [thread overview]
Message-ID: <010701d209f6$e205a030$a610e090$@gmail.com> (raw)
In-Reply-To: <edf2ee45-7793-7564-9318-ee08909d0ff5-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>
On Thu, 2016-09-08 at 02:46 +0300, Vladimir Zapolskiy wrote:
> Hi Sylvain,
>
> On 07.09.2016 22:37, Sylvain Lemieux wrote:
> > From: Sylvain Lemieux <slemieux-1xCVI8+nB4ZBDgjK7y7TUQ@public.gmane.org>
> >
> > The change setup the peripheral clock (PERIPH_CLK) as the default
> > parent clock for PWM1 & PWM2.
> >
> > Signed-off-by: Sylvain Lemieux <slemieux-1xCVI8+nB4ZBDgjK7y7TUQ@public.gmane.org>
> > ---
> > arch/arm/boot/dts/lpc32xx.dtsi | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/lpc32xx.dtsi
> > b/arch/arm/boot/dts/lpc32xx.dtsi index e295e1e..ed85b95 100644
> > --- a/arch/arm/boot/dts/lpc32xx.dtsi
> > +++ b/arch/arm/boot/dts/lpc32xx.dtsi
> > @@ -469,6 +469,9 @@
> > compatible = "nxp,lpc3220-pwm";
> > reg = <0x4005C000 0x4>;
> > clocks = <&clk LPC32XX_CLK_PWM1>;
> > + assigned-clocks = <&clk LPC32XX_CLK_PWM1>,
> > + <&clk LPC32XX_CLK_PERIPH>;
>
> I believe here "assigned-clocks = <&clk LPC32XX_CLK_PWM1>;" would be good
> enough. In this context the second clock could be potentially specified,
if you
> are going to set its rate, but because it is a common clock for many
controllers it
> should not be done from a PWM device node.
>
Good catch!
Thanks for the feedback; I will submit a version 2 of the patch.
> > + assigned-clock-parents = <&clk
> LPC32XX_CLK_PERIPH>;
> > status = "disabled";
> > };
> >
> > @@ -476,6 +479,9 @@
> > compatible = "nxp,lpc3220-pwm";
> > reg = <0x4005C004 0x4>;
> > clocks = <&clk LPC32XX_CLK_PWM2>;
> > + assigned-clocks = <&clk LPC32XX_CLK_PWM2>,
> > + <&clk LPC32XX_CLK_PERIPH>;
>
> Same as above.
>
> Please remove the second <&clk LPC32XX_CLK_PERIPH> value from the
> assigned-clocks property.
>
> > + assigned-clock-parents = <&clk
> LPC32XX_CLK_PERIPH>;
> > status = "disabled";
> > };
> >
> >
>
> --
> With best wishes,
> Vladimir
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-09-08 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 19:37 [RESEND PATCH] ARM: dts: lpc32xx: set default parent clock for pwm1 & pwm2 Sylvain Lemieux
[not found] ` <1473277073-12093-1-git-send-email-slemieux.tyco-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-07 23:46 ` Vladimir Zapolskiy
[not found] ` <edf2ee45-7793-7564-9318-ee08909d0ff5-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>
2016-09-08 17:31 ` Sylvain Lemieux [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='010701d209f6$e205a030$a610e090$@gmail.com' \
--to=slemieux.tyco-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vz-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.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 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).