Re: [PATCH 2/2] gpio: mxc: switch to dynamic allocat GPIO base

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

 



Hello,

Cc += i.MX maintainers as this file isn't matched by the MAINTAINERS entry.

On 21.08.23 14:17, Bartosz Golaszewski wrote:
> On Mon, Aug 21, 2023 at 12:21 PM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
>>
>> On Mon, Aug 21, 2023 at 9:44 AM Alexander Stein
>> <alexander.stein@xxxxxxxxxxxxxxx> wrote:
>>> Am Montag, 21. August 2023, 09:25:54 CEST schrieb Linus Walleij:
>>>> On Mon, Aug 21, 2023 at 4:47 AM Bough Chen <haibo.chen@xxxxxxx> wrote:> > Hi
>>> Linus and Bartosz,
>>>>>
>>>>> For this patch, still not in the main trunk (Linux 6.5-rc7) and
>>>>> linux-next(next-20230818). Can you help apply or any comment?
>>>>
>>>> As pointed out by Bartosz you cannot just mechanically switch the base
>>>> to -1.
>>>>
>>>> You also need to convince us that this doesn't break any systems, and if
>>>> it does, fix them so they don't break before submitting this patch.
>>>
>>> I think it's hard to tell if something breaks, this driver is used in a lot of
>>> boards. AFAIR some people are relying on the assumption of fixed order. Using
>>> dynamic allocation this not ensured. A possible fix is to use aliases [1].
>>
>> Hm I might have been to grumpy!
>>
>> It looks like any boardfiles using gpio-mxc have been eliminated
>> so this driver is now only used in device tree-boots? Right?
>>
>> Then I feel a lot better about it.
>>
>> Acked-by: Linus Walleij <linus.walleij@xxxxxxxxxx>
>>
>> Yours,
>> Linus Walleij
> 
> I will not be queueing it for v6.6 as merge window opens in a week, I
> want to give it more time in next and see if anyone complains so it'll
> make it for v6.7.

IMO, this should not be merged. I would hate to do a kernel update and
see the kernel toggle some unrelated GPIO, because probe order changes.
This will eventually happen to somebody and if they're unlucky, it will
break something.

For systems, where the order was never fixed, I agree it's on them, but
for i.MX, it has been fixed since inception AFAIK and I fail to see
what strong reason there is to justify breaking their setups in such
a manner.

Yes, the sysfs interface will eventually go away and fixed numbering
with it but that has been announced long in advance and when that happens,
updated systems with legacy scripts will cease to do GPIO until fixed
and not essentially toggling GPIOs at random.

Thanks,
Ahmad

> 
> Bart

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |





[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux