From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Clemens Gruber <clemens.gruber@pqgruber.com>
Cc: linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: pwm: pca9685: Add staggered-outputs property
Date: Fri, 20 Nov 2020 13:48:16 +0100 [thread overview]
Message-ID: <20201120124816.2ncbm75v4c5xrtw3@pengutronix.de> (raw)
In-Reply-To: <X7e4Zj1yejjLBFyl@workstation.tuxnet>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On Fri, Nov 20, 2020 at 01:36:54PM +0100, Clemens Gruber wrote:
> Hi,
>
> On Fri, Nov 20, 2020 at 09:21:50AM +0100, Uwe Kleine-König wrote:
> > On Wed, Nov 18, 2020 at 06:45:15PM +0100, Clemens Gruber wrote:
> > > The pca9685 driver supports a new staggered-outputs property for reduced
> > > current surges and EMI. This adds documentation for the new DT property.
> >
> > Maybe point out the commit that added this support here?
>
> The pca9685 driver patch was not yet accepted and there will be a v2.
>
> Should I wait until the support is in Linus' tree and only then send a
> dt-bindings documentation patch, mentioning the commit?
Then I'd say add the dt-bindings patch to the series adding this
support.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-20 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 17:45 [PATCH] dt-bindings: pwm: pca9685: Add staggered-outputs property Clemens Gruber
2020-11-20 8:21 ` Uwe Kleine-König
2020-11-20 12:36 ` Clemens Gruber
2020-11-20 12:48 ` Uwe Kleine-König [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-12 16:39 [PATCH] dt-bindings: pwm: pca9685: add " Clemens Gruber
2020-12-07 18:50 ` Rob Herring
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=20201120124816.2ncbm75v4c5xrtw3@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=clemens.gruber@pqgruber.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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).