From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, mfd@lists.linux.dev,
lee@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: mfd: ti,tps65910: Add wakeup-source and GPIO hogs
Date: Fri, 18 Sep 2026 21:05:51 +0000 [thread overview]
Message-ID: <20260918210552.5A82A1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260919-ti-tps6586x-v3-1-63dd240f4684@gmail.com>
> Device tree validation throws warnings for the TPS65911 PMIC on Tegra
> boards because wakeup-source and GPIO hog nodes are not documented in
> the schema, even though the hardware supports them.
>
> Add wakeup-source property and allow child nodes that match the "-hog"
> pattern.
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260919-ti-tps6586x-v3-0-63dd240f4684@gmail.com?part=1
next prev parent reply other threads:[~2026-09-18 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 21:01 [PATCH v3 0/4] regulator: dt-bindings: Tegra coupling DT conversions and cleanup Bhargav Joshi
2026-09-18 21:01 ` [PATCH v3 1/4] dt-bindings: mfd: ti,tps65910: Add wakeup-source and GPIO hogs Bhargav Joshi
2026-09-18 21:05 ` sashiko-bot [this message]
2026-09-23 15:18 ` (subset) " Lee Jones
2026-09-18 21:01 ` [PATCH v3 2/4] regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema Bhargav Joshi
2026-09-18 21:10 ` sashiko-bot
2026-09-23 17:44 ` Mark Brown
2026-09-18 21:01 ` [PATCH v3 3/4] regulator: dt-bindings: Reference Tegra regulator coupling schema Bhargav Joshi
2026-09-18 21:07 ` sashiko-bot
2026-09-18 21:01 ` [PATCH v3 4/4] regulator: dt-bindings: ti,tps6586x: Convert to DT schema Bhargav Joshi
2026-09-18 21:10 ` sashiko-bot
2026-09-23 17:46 ` (subset) [PATCH v3 0/4] regulator: dt-bindings: Tegra coupling DT conversions and cleanup Mark Brown
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=20260918210552.5A82A1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.bhargav.u@gmail.com \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox