[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200312172659.GZ37466@atomide.com>
Date: Thu, 12 Mar 2020 10:26:59 -0700
From: Tony Lindgren <tony@...mide.com>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Lokesh Vutla <lokeshvutla@...com>,
Thomas Gleixner <tglx@...utronix.de>,
Linux OMAP Mailing List <linux-omap@...r.kernel.org>,
linux-kernel@...r.kernel.org,
Thierry Reding <thierry.reding@...il.com>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, linux-pwm@...r.kernel.org,
Sekhar Nori <nsekhar@...com>, Tero Kristo <t-kristo@...com>
Subject: Re: [PATCH v3 0/6] clocksource: timer-ti-dm: Prepare for dynamic pwm
period updates
Hi,
* Daniel Lezcano <daniel.lezcano@...aro.org> [200312 11:11]:
> On 06/03/2020 18:19, Tony Lindgren wrote:
> > * Lokesh Vutla <lokeshvutla@...com> [200305 08:29]:
> >> This series fixes dm_timer_ops used for enabling the pwm and enables
> >> cpu_pm notifier for context save and restore. This acts as a preparatory
> >> series for enabling dynamic period updates for pwm omap dm timer driver.
> >>
> >> Changes since v2:
> >> - Incorporated changes from Tony
> >
> > I just gave this series another try here and it still works
> > for me just fine and is good to go as far as I'm concerned.
>
> How do you want this series to be merged?
>
> Shall I pick the patches falling under drivers/clocksource or ack them?
I think best would be if you picked them and applied them into
an immutable branch against v5.6-rc1 that can also be merged
into pwm driver branch as needed.
Regards,
Tony
Powered by blists - more mailing lists