From: Guru Das Srinagesh <gurus@codeaurora.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-pwm@vger.kernel.org,
"Thierry Reding" <thierry.reding@gmail.com>,
"Subbaraman Narayanamurthy" <subbaram@codeaurora.org>,
linux-kernel@vger.kernel.org, "Kamil Debski" <kamil@wypas.org>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"Jean Delvare" <jdelvare@suse.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v7 03/13] hwmon: pwm-fan: Use 64-bit division macros for period and duty cycle
Date: Tue, 10 Mar 2020 15:24:18 -0700 [thread overview]
Message-ID: <20200310222418.GA8053@codeaurora.org> (raw)
In-Reply-To: <bd6c7679-9569-2cf1-1664-61bf368d82dd@roeck-us.net>
On Tue, Mar 10, 2020 at 08:05:58AM -0700, Guenter Roeck wrote:
> I don't see support in the LED subsystem to utilize the PWM framework directly
> for blinking. Plus, you say yourself that it isn't a _real_ use case, just a
> theoretic one.
An example use case is a mobile phone OEM that wishes to set a period of
5 seconds or more for, say, a low battery slow blinking indication - currently
this is not possible. The PWM framework not having direct support for
blinking should not be a concern if the PWM peripheral being controlled
supports it via register writes.
> Either case, the reason / use case for this series should be explained
> in the summary patch. That is what it is for. That case is not made.
Will upload a new patchset adding more details in the summary patch.
Thank you.
Guru Das.
next prev parent reply other threads:[~2020-03-10 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1583782035.git.gurus@codeaurora.org>
2020-03-09 19:35 ` [PATCH v7 03/13] hwmon: pwm-fan: Use 64-bit division macros for period and duty cycle Guru Das Srinagesh
2020-03-09 21:48 ` Guenter Roeck
2020-03-10 12:08 ` Uwe Kleine-König
2020-03-10 15:05 ` Guenter Roeck
2020-03-10 22:24 ` Guru Das Srinagesh [this message]
2020-03-10 22:57 ` Guenter Roeck
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=20200310222418.GA8053@codeaurora.org \
--to=gurus@codeaurora.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=jdelvare@suse.com \
--cc=kamil@wypas.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=subbaram@codeaurora.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).