Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: mfd@lists.linux.dev, devicetree@vger.kernel.org, robh@kernel.org,
	lee@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: mfd: ti,tps65910: Add wakeup-source and GPIO hogs
Date: Wed, 16 Sep 2026 13:18:27 +0000	[thread overview]
Message-ID: <20260916131827.9784F1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260916-ti-tps6586x-v2-1-f12cfdfb446c@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.
> 
> 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/20260916-ti-tps6586x-v2-0-f12cfdfb446c@gmail.com?part=1


  reply	other threads:[~2026-09-16 13:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 13:11 [PATCH v2 0/4] regulator: dt-bindings: Tegra coupling DT conversions and cleanup Bhargav Joshi
2026-09-16 13:11 ` [PATCH v2 1/4] dt-bindings: mfd: ti,tps65910: Add wakeup-source and GPIO hogs Bhargav Joshi
2026-09-16 13:18   ` sashiko-bot [this message]
2026-09-18 19:09   ` Rob Herring (Arm)
2026-09-16 13:11 ` [PATCH v2 2/4] regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema Bhargav Joshi
2026-09-16 13:23   ` sashiko-bot
2026-09-18 19:06   ` Rob Herring
2026-09-16 13:11 ` [PATCH v2 3/4] regulator: dt-bindings: Reference Tegra regulator coupling schema Bhargav Joshi
2026-09-16 13:20   ` sashiko-bot
2026-09-18 19:06   ` Rob Herring
2026-09-16 13:11 ` [PATCH v2 4/4] regulator: dt-bindings: ti,tps6586x: Convert to DT schema Bhargav Joshi
2026-09-16 13:21   ` sashiko-bot
2026-09-18 19:08   ` Rob Herring (Arm)
2026-10-01 22:59   ` 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=20260916131827.9784F1F00893@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