From: Thierry Reding <thierry.reding@avionic-design.de>
To: Lars Poeschel <poeschel@lemonage.de>
Cc: Lars Poeschel <larsi@wh2.tu-dresden.de>,
rob@landley.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v1] pwm: add sysfs interface
Date: Mon, 8 Apr 2013 13:34:58 +0200 [thread overview]
Message-ID: <20130408113457.GA17028@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <201304081315.37794.poeschel@lemonage.de>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Mon, Apr 08, 2013 at 01:15:37PM +0200, Lars Poeschel wrote:
[...]
> You mean change only while a PWM is disabled ?Ok, as said above, I need to be
> able to change at least the duty cycle while the PWM is running without
> having gaps. But prohibiting changes of the period could be done with
> returning -EBUSY.
Okay, that sounds acceptable. duty-cycle should be the only value that
can be changed while a PWM is enabled. Obviously it should still return
-EINVAL if the duty-cycle is larger than the period, but the PWM core
will take care of that automatically.
By the way, would you mind elaborating a bit on the various use-cases
that you have? I'm interested in what people use the PWM subsystem for
and you seem to be the only one currently using it from userspace. I'm
hoping I can get a better understanding of what the PWM subsystem nedes
to provide if I know what people use it for.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-08 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 13:58 [PATCH v1] pwm: add sysfs interface Lars Poeschel
2013-04-08 8:17 ` Thierry Reding
[not found] ` <201304081315.37794.poeschel@lemonage.de>
2013-04-08 11:34 ` Thierry Reding [this message]
2013-04-09 9:21 ` Lars Poeschel
-- strict thread matches above, loose matches on Subject: below --
2013-04-08 11:55 Lars Poeschel
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=20130408113457.GA17028@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=larsi@wh2.tu-dresden.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=poeschel@lemonage.de \
--cc=rob@landley.net \
/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