From: sashiko-bot@kernel.org
To: "Samuel Holland" <samuel@sholland.org>
Cc: devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org, lee@kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: leds: Document "gpio" trigger
Date: Sat, 11 Jul 2026 19:32:52 +0000 [thread overview]
Message-ID: <20260711193253.359F61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260711192842.845048-2-samuel@sholland.org>
> The "gpio" trigger is used to control LEDs by the level of a GPIO input
> referenced by the trigger-sources property. This is already documented
> in the trigger-sources property description and is used in at least one
> devicetree (am335x-regor.dtsi). Document it so validation of those and
> future DTs will pass.
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260711192842.845048-1-samuel@sholland.org?part=1
next prev parent reply other threads:[~2026-07-11 19:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 19:28 [PATCH 0/4] Add devicetree for LincPlus LincStation E1 Samuel Holland
2026-07-11 19:28 ` Samuel Holland
2026-07-11 19:28 ` [PATCH 1/4] dt-bindings: leds: Document "gpio" trigger Samuel Holland
2026-07-11 19:28 ` Samuel Holland
2026-07-11 19:32 ` sashiko-bot [this message]
2026-07-13 16:20 ` Conor Dooley
2026-07-13 16:20 ` Conor Dooley
2026-07-11 19:28 ` [PATCH 2/4] dt-bindings: vendor-prefixes: Add techvision Samuel Holland
2026-07-11 19:28 ` Samuel Holland
2026-07-11 19:29 ` sashiko-bot
2026-07-13 16:20 ` Conor Dooley
2026-07-13 16:20 ` Conor Dooley
2026-07-11 19:28 ` [PATCH 3/4] dt-bindings: arm: rockchip: Add LincStation E1 Samuel Holland
2026-07-11 19:28 ` Samuel Holland
2026-07-11 19:30 ` sashiko-bot
2026-07-13 16:22 ` Conor Dooley
2026-07-13 16:22 ` Conor Dooley
2026-07-11 19:28 ` [PATCH 4/4] arm64: dts: " Samuel Holland
2026-07-11 19:28 ` Samuel Holland
2026-07-11 19:35 ` sashiko-bot
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=20260711193253.359F61F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.