From: Sean Young <sean@mess.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Maíra Canal" <maira.canal@usp.br>,
mchehab@kernel.org, thierry.reding@gmail.com,
lee.jones@linaro.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [PATCH v4] media: rc: pwm-ir-tx: Switch to atomic PWM API
Date: Sun, 31 Oct 2021 10:39:34 +0000 [thread overview]
Message-ID: <20211031103933.GA28316@gofer.mess.org> (raw)
In-Reply-To: <20211028111535.x7xgz7domx2lpyfh@pengutronix.de>
Hi Uwe,
On Thu, Oct 28, 2021 at 01:15:35PM +0200, Uwe Kleine-König wrote:
> On Thu, Oct 28, 2021 at 10:14:42AM +0100, Sean Young wrote:
> > We still have the problem that the pwm drivers calculate the period
> > incorrectly by rounding down (except pwm-bcm2835). So the period is not
> > as good as it could be in most cases, but this driver can't do anything
> > about that.
>
> Yeah, some time ago I started coding a round_state function
> (wip at
> https://git.pengutronix.de/cgit/ukl/linux/commit/?h=pwm-wip&id=ae348eb6a55d6526f30ef4a49819197d9616391e)
> but this was pushed down on my todo-list by more important stuff.
>
> If you want to experiment with that ...
I was thinking about this problem this morning.
- The pwm-ir-tx driver gets a carrier set in Hz, which it has to convert to
a period (1e9 / carrier). There is loss of accuracy there.
- When it gets to the pwm driver, the period is converted into the format
the pwm hardware expects. For example the pwm-bcm2835 driver converts
it into clock cycles (1e9 / 8e8).
Both calculations involve loss of accuracy because of integer representation.
Would it make more sense for the pwm interface to use numer/denom rational
numbers?
struct rational {
u64 numer;
u64 denom;
};
If pwm-ir-tx would like to set the carrier, it could it like so:
struct rational period = {
.numer = NUSEC_PER_SEC,
.denom = carrier,
};
pwm_set_period(&period);
Now pwm-bcm2835 could do it like so:
int bcm2835_set_period(struct rational *period)
{
struct rational rate = {
.numer = NUSEC_PER_SEC,
.denum = clk_get_rate(clk),
};
rational_div(&rate, period);
int step = rational_to_u64(&rate);
}
Alternatively, since most of the pwm hardware is doing scaling based on the
clock (I think), would not make more sense for the pwm driver interface to
take a frequency rather than a period? Then the integer calculations can be
simpler: just divide the clock rate by the required frequency and you have
the period.
Just some thoughts.
Sean
next prev parent reply other threads:[~2021-10-31 10:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 15:34 [PATCH v4] media: rc: pwm-ir-tx: Switch to atomic PWM API Maíra Canal
2021-10-28 6:45 ` Uwe Kleine-König
2021-10-28 9:14 ` Sean Young
2021-10-28 11:15 ` Uwe Kleine-König
2021-10-28 12:26 ` Sean Young
2021-10-28 18:05 ` Uwe Kleine-König
2021-10-29 7:16 ` Sean Young
2021-10-29 11:06 ` Uwe Kleine-König
2021-10-29 11:54 ` Sean Young
2021-10-29 12:08 ` Maíra Canal
2021-10-29 15:18 ` Uwe Kleine-König
2021-10-30 9:21 ` Sean Young
2021-10-31 10:39 ` Sean Young [this message]
2021-10-31 17:40 ` Uwe Kleine-König
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=20211031103933.GA28316@gofer.mess.org \
--to=sean@mess.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=maira.canal@usp.br \
--cc=mchehab@kernel.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