public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: linux-i2c@vger.kernel.org,
	Alexander Stein <alexander.stein@ew.tq-group.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org, kernel@dh-electronics.com
Subject: Re: [PATCH 1/2] dt-bindings: at24: add ST M24256E Additional Write lockable page support
Date: Fri, 18 Oct 2024 08:27:54 -0500	[thread overview]
Message-ID: <20241018132754.GA54765-robh@kernel.org> (raw)
In-Reply-To: <20241017184152.128395-1-marex@denx.de>

On Thu, Oct 17, 2024 at 08:41:25PM +0200, Marek Vasut wrote:
> The ST M24256E behaves as a regular M24C256, except for the E variant
> which uses up another I2C address for Additional Write lockable page.
> This page is 64 Bytes long and can contain additional data. Add entry
> for it, so users can describe that page in DT. Note that users still
> have to describe the main M24C256 area separately as that is on separate
> I2C address from this page.

I think this should be modelled as 1 node having 2 addresses, not 2 
nodes.

> 
> Unlike M24C32-D and M24C64-D, this part is specifically ST and does not
> have any comparable M24* counterparts from other vendors, hence the st,
> vendor prefix. Furthermore, the part name is M24256E without C between
> the 24 and 256, this is not a typo. Finally, there is M24C256-D part,
> which does contain 32 Bytes long Additional Write lockable page, which
> is a different part and not supported by this patch.
> 
> Datasheet: https://www.st.com/resource/en/datasheet/m24256e-f.pdf
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Alexander Stein <alexander.stein@ew.tq-group.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> Cc: Bartosz Golaszewski <brgl@bgdev.pl>
> Cc: Christoph Niedermaier <cniedermaier@dh-electronics.com>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Rob Herring <robh@kernel.org>
> Cc: devicetree@vger.kernel.org
> Cc: kernel@dh-electronics.com
> Cc: linux-i2c@vger.kernel.org
> ---
>  Documentation/devicetree/bindings/eeprom/at24.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/eeprom/at24.yaml b/Documentation/devicetree/bindings/eeprom/at24.yaml
> index b6239ec3512b3..590ba0ef5fa26 100644
> --- a/Documentation/devicetree/bindings/eeprom/at24.yaml
> +++ b/Documentation/devicetree/bindings/eeprom/at24.yaml
> @@ -141,6 +141,8 @@ properties:
>            - const: microchip,24aa025e48
>        - items:
>            - const: microchip,24aa025e64
> +      - items:
> +          - const: st,24256e-wl
>        - pattern: '^atmel,24c(32|64)d-wl$' # Actual vendor is st
>  
>    label:
> -- 
> 2.45.2
> 

  parent reply	other threads:[~2024-10-18 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 18:41 [PATCH 1/2] dt-bindings: at24: add ST M24256E Additional Write lockable page support Marek Vasut
2024-10-17 18:41 ` [PATCH 2/2] eeprom: " Marek Vasut
2024-10-18 13:27 ` Rob Herring [this message]
2024-10-20  4:29   ` [PATCH 1/2] dt-bindings: " Marek Vasut
2024-10-21 18:14     ` Rob Herring
2024-10-21 18:35       ` Bartosz Golaszewski
2024-11-19 11:01         ` Geert Uytterhoeven
2024-11-19 12:04           ` Bartosz Golaszewski
2024-10-22  7:13 ` Bartosz Golaszewski
2024-10-22  7:14   ` Bartosz Golaszewski

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=20241018132754.GA54765-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=arnd@arndb.de \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=cniedermaier@dh-electronics.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@dh-electronics.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=marex@denx.de \
    /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