From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "David Lechner" <david@lechnology.com>,
linux-iio@vger.kernel.org, linux-omap@vger.kernel.org,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"William Breathitt Gray" <vilhelm.gray@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH v3 1/6] bus/ti-pwmss: move TI PWMSS driver from PWM to bus subsystem
Date: Sun, 8 Sep 2019 12:15:24 +0100 [thread overview]
Message-ID: <20190908121524.49b4874d@archlinux> (raw)
In-Reply-To: <20190902150245.GE1445@ulmo>
On Mon, 2 Sep 2019 17:02:45 +0200
Thierry Reding <thierry.reding@gmail.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@lechnology.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@gmail.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.
Thanks,
Jonathan
next prev parent reply other threads:[~2019-09-08 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 22:58 [PATCH v3 0/6] counter: new TI eQEP driver David Lechner
2019-09-01 22:58 ` [PATCH v3 1/6] bus/ti-pwmss: move TI PWMSS driver from PWM to bus subsystem David Lechner
2019-09-02 15:02 ` Thierry Reding
2019-09-08 11:15 ` Jonathan Cameron [this message]
2019-09-08 19:44 ` Tony Lindgren
2019-10-17 20:58 ` Jonathan Cameron
2019-09-01 22:58 ` [PATCH v3 2/6] dt-bindings: counter: new bindings for TI eQEP David Lechner
2019-09-02 15:02 ` Rob Herring
2019-09-01 22:58 ` [PATCH v3 3/6] counter: new TI eQEP driver David Lechner
2019-09-01 22:58 ` [PATCH v3 4/6] ARM: dts: am33xx: Add nodes for eQEP David Lechner
2019-09-01 22:58 ` [PATCH v3 5/6] ARM: dts: am335x-boneblue: Enable eQEP David Lechner
2019-09-02 14:17 ` [PATCH v3 0/6] counter: new TI eQEP driver David Lechner
2019-09-05 13:37 ` William Breathitt Gray
2019-09-05 14:10 ` Tony Lindgren
2019-09-08 11:16 ` Jonathan Cameron
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=20190908121524.49b4874d@archlinux \
--to=jic23@jic23.retrosnub.co.uk \
--cc=bcousson@baylibre.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=vilhelm.gray@gmail.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).