[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190908194447.GM52127@atomide.com>
Date: Sun, 8 Sep 2019 12:44:48 -0700
From: Tony Lindgren <tony@...mide.com>
To: Jonathan Cameron <jic23@...23.retrosnub.co.uk>
Cc: Thierry Reding <thierry.reding@...il.com>,
David Lechner <david@...hnology.com>,
linux-iio@...r.kernel.org, linux-omap@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
BenoƮt Cousson <bcousson@...libre.com>,
William Breathitt Gray <vilhelm.gray@...il.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pwm@...r.kernel.org
Subject: Re: [PATCH v3 1/6] bus/ti-pwmss: move TI PWMSS driver from PWM to
bus subsystem
* Jonathan Cameron <jic23@...23.retrosnub.co.uk> [190908 11:16]:
> On Mon, 2 Sep 2019 17:02:45 +0200
> Thierry Reding <thierry.reding@...il.com> wrote:
>
> > On Sun, Sep 01, 2019 at 05:58:22PM -0500, David Lechner wrote:
> > > The TI PWMSS driver is a simple bus driver for providing power
> > > power management for the PWM peripherals on TI AM33xx SoCs, namely
> > > eCAP, eHRPWM and eQEP. The eQEP is a counter rather than a PWM, so
> > > it does not make sense to have the bus driver in the PWM subsystem
> > > since the PWMSS is not exclusive to PWM devices.
> > >
> > > Signed-off-by: David Lechner <david@...hnology.com>
> > > ---
> > >
> > > v3 changes:
> > > - none
> > > v2 changes:
> > > - new patch
> > >
> > > drivers/bus/Kconfig | 9 +++++++++
> > > drivers/bus/Makefile | 1 +
> > > drivers/{pwm/pwm-tipwmss.c => bus/ti-pwmss.c} | 0
> > > drivers/pwm/Kconfig | 9 ---------
> > > drivers/pwm/Makefile | 1 -
> > > 5 files changed, 10 insertions(+), 10 deletions(-)
> > > rename drivers/{pwm/pwm-tipwmss.c => bus/ti-pwmss.c} (100%)
> >
> > Acked-by: Thierry Reding <thierry.reding@...il.com>
>
> Do we need an immutable branch for these precursor patches to the
> driver addition? It's not going to make 5.4 via my tree as cutting it
> too fine so we'll be in the position of holding these in a non obvious
> tree for a whole cycle.
Sure an immutable branch would be nice in case of unlikely
dts file conflicts. And yeah no need to try to rush to v5.4.
Regards,
Tony
Powered by blists - more mailing lists