From: Roman Vivchar via B4 Relay <devnull+rva333.protonmail.com@kernel.org>
To: Sean Young <sean@mess.org>, Lee Jones <lee@kernel.org>,
Pavel Machek <pavel@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-media@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Roman Vivchar <rva333@protonmail.com>
Subject: [PATCH 0/2] media: pwm-ir-tx: regulator support
Date: Mon, 02 Nov 2026 17:22:55 +0200 [thread overview]
Message-ID: <20261102-6768-irled-v1-0-c7064f3afed1@protonmail.com> (raw)
This patch series adds optional power-supply property for PWM IR LED,
because some boards, like Xiaomi Redmi Note 9 phone, have the LED
connected to the eMMC power rail. If the eMMC is powered down, IR LED
can't function.
Patch 1 adds dt-bindings documentation for the power-supply property.
Patch 2 adds regulator management to the driver.
Signed-off-by: Roman Vivchar <rva333@protonmail.com>
---
Roman Vivchar (2):
dt-bindings: leds: irled: pwm-ir-tx: add power supply support
media: pwm-ir-tx: add regulator support
.../devicetree/bindings/leds/irled/pwm-ir-tx.yaml | 4 +++
drivers/media/rc/pwm-ir-tx.c | 37 +++++++++++++++++++++-
2 files changed, 40 insertions(+), 1 deletion(-)
---
base-commit: 5e6de6a2b522f659defacb1551d0465ba6ce13cf
change-id: 20261102-6768-irled-9e368faa84a7
Best regards,
--
Roman Vivchar <rva333@protonmail.com>
next reply other threads:[~2026-11-02 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 15:22 Roman Vivchar via B4 Relay [this message]
2026-11-02 15:22 ` [PATCH 1/2] dt-bindings: leds: irled: pwm-ir-tx: add power supply support Roman Vivchar via B4 Relay
2026-11-06 12:54 ` Krzysztof Kozlowski
2026-11-02 15:22 ` [PATCH 2/2] media: pwm-ir-tx: add regulator support Roman Vivchar via B4 Relay
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=20261102-6768-irled-v1-0-c7064f3afed1@protonmail.com \
--to=devnull+rva333.protonmail.com@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=rva333@protonmail.com \
--cc=sean@mess.org \
/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
all inboxes | Powered by JetHome®