From: Olliver Schinagl <oliver@schinagl.nl>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: "thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>,
"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: Fri, 25 Sep 2020 20:14:58 +0200 [thread overview]
Message-ID: <cbb303e9-a352-ec2e-691d-4e073bbee8c0@schinagl.nl> (raw)
In-Reply-To: <20200915140208.bzserxn2bgw4xiwk@axis.com>
Hey Vincent,
On 15-09-2020 16:02, Vincent Whitchurch wrote:
> On Thu, Sep 03, 2020 at 11:15:31AM +0200, Olliver Schinagl wrote:
>> On 14-08-2020 17:55, Vincent Whitchurch wrote:
>>> Add a software PWM which toggles a GPIO from a high-resolution timer.
>>>
>>> This will naturally not be as accurate or as efficient as a hardware
>>> PWM, but it is useful in some cases. I have for example used it for
>>> evaluating LED brightness handling (via leds-pwm) on a board where the
>>> LED was just hooked up to a GPIO, and for a simple verification of the
>>> timer frequency on another platform.
>>>
>>> Since high-resolution timers are used, sleeping gpio chips are not
>>> supported and are rejected in the probe function.
>>>
>>> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
>>> ---
>>> While preparing this driver for posting, I found a pwm-gpio driver posted to
>>> the lists way back in 2015 by Olliver Schinagl:
>>>
>>> https://lore.kernel.org/linux-pwm/1445895161-2317-8-git-send-email-o.schinagl@ultimaker.com/
>>>
>> Thanks for reminding me there :) As I think I still use this driver, I
>> don't mind migrating to this one (if merged) but how do you suggests to
>> proceed with regards to multiple PWM's, as this is how I am using it
>> currently. E.g. how do we merge them? I'm fine with 'taking the simpler
>> code method' for a start point, but i guess I solved that part
>> (somewhat) in 2015 :p
>
> 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'?
Olliver
next prev parent reply other threads:[~2020-09-25 18: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 [this message]
2020-09-26 13:24 ` Uwe Kleine-König
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=cbb303e9-a352-ec2e-691d-4e073bbee8c0@schinagl.nl \
--to=oliver@schinagl.nl \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=lee.jones@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--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).