From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Olliver Schinagl <oliver@schinagl.nl>
Cc: Vincent Whitchurch <vincent.whitchurch@axis.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
kernel <kernel@axis.com>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: Re: [PATCH 2/2] pwm: Add GPIO PWM driver
Date: Sat, 26 Sep 2020 15:24:48 +0200 [thread overview]
Message-ID: <20200926132448.fnjeehot2h6iazdd@pengutronix.de> (raw)
In-Reply-To: <cbb303e9-a352-ec2e-691d-4e073bbee8c0@schinagl.nl>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Hello Olliver,
On Fri, Sep 25, 2020 at 08:14:58PM +0200, Olliver Schinagl wrote:
> On 15-09-2020 16:02, Vincent Whitchurch wrote:
> > Since this is just a software construct, the simplest way would just be
> > to create multiple instances in the device tree if you want multiple
> > PWMs, wouldn't it?
>
> Not entirely, as they are no longer 'logically grouped'?
Why is it necessary for you that the PWMs are "logically grouped"?
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-09-26 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 15:55 [PATCH 1/2] dt-bindings: pwm: Add pwm-gpio Vincent Whitchurch
2020-08-14 15:55 ` [PATCH 2/2] pwm: Add GPIO PWM driver Vincent Whitchurch
2020-08-15 7:50 ` Uwe Kleine-König
2020-09-02 12:11 ` Vincent Whitchurch
2020-09-02 18:00 ` Uwe Kleine-König
2020-09-03 9:15 ` Olliver Schinagl
2020-09-15 14:02 ` Vincent Whitchurch
2020-09-25 18:14 ` Olliver Schinagl
2020-09-26 13:24 ` Uwe Kleine-König [this message]
2020-08-17 19:38 ` [PATCH 1/2] dt-bindings: pwm: Add pwm-gpio Rob Herring
2020-09-02 12:08 ` Vincent Whitchurch
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=20200926132448.fnjeehot2h6iazdd@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=lee.jones@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--cc=oliver@schinagl.nl \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vincent.whitchurch@axis.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).