Re: [PATCH] nvmem: core: eeprom: at24: Handle EEPROM with both read-only and wp-gpios

[Bartosz Golaszewski]

On Tue, Apr 21, 2026 at 4:08 PM Marek Vasut <marex@xxxxxxxxxxxx> wrote:
>
> Handle special-case of AT24 EEPROM described in DT, which contains both
> "read-only" and "wp-gpios" properties. Interpret this configuration as
> default read-only, but with the possibility of unlock via force_ro sysfs
> attribute.
>

Patch looks ok code-wise but does this really make sense? If an EEPROM
is read-only, we should forbid writes in the kernel. Which board uses
it? Can we simply remove the read-only flag from DT?

Admittedly: the DT bindings do allow it as read-only and wp-gpios are
not mutually exclusive but I think it's more of an accidental omission
than a planned feature.

Bart