[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176217924320.53912.4328025839514313502.b4-ty@linaro.org>
Date: Mon,  3 Nov 2025 15:14:12 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	Daniel Scally <djrscally@...il.com>,
	Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
	Sakari Ailus <sakari.ailus@...ux.intel.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	Danilo Krummrich <dakr@...nel.org>,
	Philipp Zabel <p.zabel@...gutronix.de>,
	Krzysztof Kozlowski <krzk@...nel.org>,
	Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org
Subject: Re: (subset) [PATCH v4 00/10] reset: rework reset-gpios handling
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
On Mon, 03 Nov 2025 10:35:20 +0100, Bartosz Golaszewski wrote:
> Software node maintainers: if this versions is good to go, can you leave
> your Acks under patches 1-3 and allow Philipp to take it through the
> reset tree, provided he creates an immutable branch you can pull from
> for v6.19?
> 
> Machine GPIO lookup is a nice, if a bit clunky, mechanism when we have
> absolutely no idea what the GPIO provider is or when it will be created.
> However in the case of reset-gpios, we not only know if the chip is
> there - we also already hold a reference to its firmware node.
> 
> [...]
Applied, thanks!
[04/10] gpio: swnode: don't use the swnode's name as the key for GPIO lookup
        https://git.kernel.org/brgl/linux/c/e5d527be7e6984882306b49c067f1fec18920735
Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Powered by blists - more mailing lists