From: Marek Vasut <marex@nabladev.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-i2c@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Srinivas Kandagatla <srini@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: core: eeprom: at24: Handle EEPROM with both read-only and wp-gpios
Date: Thu, 23 Apr 2026 16:06:36 +0200 [thread overview]
Message-ID: <bcbcc7b6-dede-4918-b229-bf546fb1742c@nabladev.com> (raw)
In-Reply-To: <CAMRc=Mfam_wONk+chgEi_hefBj+2+zhcSfbo0=Lxr_vOnvL1MA@mail.gmail.com>
On 4/23/26 2:17 PM, Bartosz Golaszewski wrote:
> On Thu, Apr 23, 2026 at 2:04 PM Marek Vasut <marex@nabladev.com> wrote:
>>
>>>
>>> I see. Ok, please send a v2.
>> Does this patch require any changes ?
>>
>> I will be sending the DT changes separately.
>
> Sashiko is saying this:
> https://sashiko.dev/#/patchset/20260421140755.54222-1-marex%40nabladev.com
What does this mean ?
> Shouldn't we report the device as read-only in sysfs unless it was
> "unlocked" with force_ro?
This would be ideal, but I did not find a way to toggle the "nvmem" bin
attr permissions at runtime. Is that even possible ?
next prev parent reply other threads:[~2026-04-23 14:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 14:06 [PATCH] nvmem: core: eeprom: at24: Handle EEPROM with both read-only and wp-gpios Marek Vasut
2026-04-22 9:07 ` Bartosz Golaszewski
2026-04-22 11:33 ` Marek Vasut
2026-04-22 17:01 ` Marek Vasut
2026-04-23 7:42 ` Bartosz Golaszewski
2026-04-23 9:37 ` Marek Vasut
2026-04-23 12:17 ` Bartosz Golaszewski
2026-04-23 14:06 ` Marek Vasut [this message]
2026-04-23 14:19 ` Bartosz Golaszewski
2026-04-23 19:15 ` Marek Vasut
2026-04-24 8:12 ` Bartosz Golaszewski
2026-04-26 2:49 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bcbcc7b6-dede-4918-b229-bf546fb1742c@nabladev.com \
--to=marex@nabladev.com \
--cc=arnd@arndb.de \
--cc=brgl@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srini@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox