Re: [PATCH] leds: Delete GPIO LED trigger

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


On Tue, Mar 14, 2023 at 9:29 PM Pavel Machek <pavel@xxxxxx> wrote:

> > We have since moved to dynamic allocation of GPIO numbers
> > and there is no real guarantee that a GPIO number will stay
> > consistent even across a reboot: consider a USB attached
> > GPIO controller for example. Or two. Or the effect of
> > probe order after adding -EPROBE_DEFER to the kernel.
> So... what? If your system is one of those with single GPIO
> controller, you can still use it. If you have modern "complex" system,
> your userspace can find out desired GPIO number and then use it.

It's not about the complexity of the GPIO controller but
whether it uses static GPIO number allocations.
One of the GPIO controllers that nowadays use dynamic
GPIO number allocation is the OMAP controller.

> Likely noone will miss this trigger, but correct way is to mark it as
> deprecated / broken in Kconfig, first, and see who screams.

OK fair enough I'll send a patch like that.

Linus Walleij

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

  Powered by Linux