Devicetree
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,  Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Thierry Reding <thierry.reding@avionic-design.de>,
	 Lee Jones <lee@kernel.org>,
	Shree Ramamoorthy <s-ramamoorthy@ti.com>,
	 Thierry Reding <thierry.reding@kernel.org>,
	 Jonathan Hunter <jonathanh@nvidia.com>,
	Dmitry Osipenko <digetx@gmail.com>,
	 Svyatoslav Ryhel <clamor95@gmail.com>,
	 Laxman Dewangan <ldewangan@nvidia.com>,
	 Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	 goledhruva@gmail.com, m-chawdhry@ti.com,
	daniel.baluta@gmail.com,  simona.toaca@nxp.com,
	mfd@lists.linux.dev,  Thierry Reding <treding@nvidia.com>,
	linux-tegra@vger.kernel.org
Subject: Re: (subset) [PATCH v3 1/4] dt-bindings: mfd: ti,tps65910: Add wakeup-source and GPIO hogs
Date: Wed, 23 Sep 2026 16:18:59 +0100	[thread overview]
Message-ID: <179017673997.4161889.6046857782031846355.b4-ty@b4> (raw)
In-Reply-To: <20260919-ti-tps6586x-v3-1-63dd240f4684@gmail.com>

On Sat, 19 Sep 2026 02:31:22 +0530, Bhargav Joshi wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/4] dt-bindings: mfd: ti,tps65910: Add wakeup-source and GPIO hogs
      commit: 6d39f6cc5ae3a84bccc9acf11ef71e7219c3d35e

--
Lee Jones [李琼斯]


  parent reply	other threads:[~2026-09-23 15:19 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
2026-09-23 15:18   ` Lee Jones [this message]
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=179017673997.4161889.6046857782031846355.b4-ty@b4 \
    --to=lee@kernel.org \
    --cc=broonie@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=goledhruva@gmail.com \
    --cc=j.bhargav.u@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=m-chawdhry@ti.com \
    --cc=mfd@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=s-ramamoorthy@ti.com \
    --cc=simona.toaca@nxp.com \
    --cc=thierry.reding@avionic-design.de \
    --cc=thierry.reding@kernel.org \
    --cc=treding@nvidia.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