From: Sean Young <sean@mess.org>
To: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Cc: Sean Young <sean@mess.org>, linux-riscv@lists.infradead.org
Subject: [PATCH 0/2] Improve pwm-ir-tx precision
Date: Sun, 1 Oct 2023 11:40:28 +0100 [thread overview]
Message-ID: <cover.1696156485.git.sean@mess.org> (raw)
The pwm-ir-tx driver has to turn the pwm signal on and off, and suffers
from delays as this is done in process context. Make this work in atomic
context.
Sean Young (2):
pwm: make it possible to apply pwm changes in atomic context
media: pwm-ir-tx: trigger edges from hrtimer interrupt context
drivers/media/rc/pwm-ir-tx.c | 79 +++++++++++++++++++++++++-------
drivers/pwm/core.c | 2 +-
drivers/pwm/pwm-fsl-ftm.c | 1 +
drivers/pwm/pwm-imx-tpm.c | 1 +
drivers/pwm/pwm-iqs620a.c | 1 +
drivers/pwm/pwm-lpc18xx-sct.c | 1 +
drivers/pwm/pwm-microchip-core.c | 1 +
drivers/pwm/pwm-omap-dmtimer.c | 1 +
drivers/pwm/pwm-pca9685.c | 1 +
drivers/pwm/pwm-renesas-tpu.c | 1 -
drivers/pwm/pwm-rz-mtu3.c | 1 +
drivers/pwm/pwm-sifive.c | 1 +
drivers/pwm/pwm-sti.c | 1 +
drivers/pwm/pwm-stm32.c | 1 +
drivers/pwm/pwm-twl-led.c | 1 +
drivers/pwm/pwm-twl.c | 1 +
include/linux/pwm.h | 27 +++++++++--
17 files changed, 100 insertions(+), 22 deletions(-)
--
2.42.0
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-10-01 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 10:40 Sean Young [this message]
2023-10-01 10:40 ` [PATCH 1/2] pwm: make it possible to apply pwm changes in atomic context Sean Young
2023-10-01 14:43 ` kernel test robot
2023-10-01 16:07 ` kernel test robot
2023-10-01 17:21 ` Sean Young
2023-10-04 9:59 ` Uwe Kleine-König
2023-10-05 8:30 ` Sean Young
2023-10-05 9:17 ` Uwe Kleine-König
2023-10-06 10:27 ` Thierry Reding
2023-10-06 14:44 ` Uwe Kleine-König
2023-10-06 10:29 ` Thierry Reding
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=cover.1696156485.git.sean@mess.org \
--to=sean@mess.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).