From: Tony Lindgren <tony@atomide.com>
To: Suman Anna <s-anna@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>, Tero Kristo <t-kristo@ti.com>,
Sekhar Nori <nsekhar@ti.com>, Rob Herring <robh+dt@kernel.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH] arm: dts: Add 32KHz clock as default clock source
Date: Tue, 5 May 2020 11:02:43 -0700 [thread overview]
Message-ID: <20200505180243.GM37466@atomide.com> (raw)
In-Reply-To: <e49e047d-6883-6bee-7dac-a544a27f6293@ti.com>
* Suman Anna <s-anna@ti.com> [200505 16:07]:
> On 4/28/20 1:19 PM, Tony Lindgren wrote:
> > * Lokesh Vutla <lokeshvutla@ti.com> [200427 17:27]:
> > > Clocksource to timer configured in pwm mode can be selected using the DT
> > > property ti,clock-source. There are few pwm timers which are not
> > > selecting the clock source and relying on default value in hardware or
> > > selected by driver. Instead of relying on default value, always select
> > > the clock source from DT.
> > >
> > > Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
>
> Thanks Lokesh, with this patch, we should be able to pickup the dmtimer
> driver patch to finally allow dmtimer clients to use assigned-clock-parents.
>
> Once both of these are merged, we can deprecate the ti,clock-source from the
> omap-pwm-dmtimer driver.
>
> Reviewed-by: Suman Anna <s-anna@ti.com>
I've pushed this patch applied against v5.7-rc1 into
omap-for-v5.8/dt-timer.
Regards,
Tony
prev parent reply other threads:[~2020-05-05 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 17:26 [PATCH] arm: dts: Add 32KHz clock as default clock source Lokesh Vutla
2020-04-28 18:19 ` Tony Lindgren
2020-05-05 16:06 ` Suman Anna
2020-05-05 18:02 ` Tony Lindgren [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=20200505180243.GM37466@atomide.com \
--to=tony@atomide.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.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).