Re: [PATCH v6 4/6] reset: Instantiate reset GPIO controller for shared reset-gpios

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 31, 2024 at 02:42:17PM +0100, Linus Walleij wrote:

> I guess it may be an issue that regulators are not using Device Tree
> exclusively, but also has to deal with a slew of platform_devices:s :/
> IIRC that was one of the reasons why it looks as it does.

Also ACPI, and this is a long standing binding so we can't change the
ABI for DT.  We could potentially use a refcounting mechanism provided
by the GPIO core but we'd need to know when the refcount changes from 0
to 1 and back, we need to take other actions (inserting delays and
generating notifications) when it does so I'm not sure how exciting it
is to factor out the refcount.  I think part of the decision making with
the current design was that there was likely going to need to be some
higher level stuff like that in the users so it wasn't clear that trying
to abstract the reference count away in gpiolib was buying us much.

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux