From: Marek Vasut <marex@denx.de>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-i2c@vger.kernel.org
Cc: devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] eeprom: at24: add ST M24C64-D Additional Write lockable page support
Date: Fri, 13 Oct 2023 13:30:56 +0200 [thread overview]
Message-ID: <0120031f-5b08-44ee-b6a1-b2ea38f8c001@denx.de> (raw)
In-Reply-To: <20231013063008.2879314-2-alexander.stein@ew.tq-group.com>
On 10/13/23 08:30, Alexander Stein wrote:
> The ST M24C64-D behaves as a regular M24C64, except for the -D variant
> which uses up another I2C address for Additional Write lockable page.
> This page is 32 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 M24C64 area separately as that is on separate
> I2C address from this page.
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Reviewed-by: Marek Vasut <marex@denx.de>
next prev parent reply other threads:[~2023-10-13 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 6:30 [PATCH 1/2] dt-bindings: at24: add ST M24C64-D Additional Write lockable page Alexander Stein
2023-10-13 6:30 ` [PATCH 2/2] eeprom: at24: add ST M24C64-D Additional Write lockable page support Alexander Stein
2023-10-13 11:30 ` Marek Vasut [this message]
2023-10-16 6:50 ` Bartosz Golaszewski
2023-10-13 11:35 ` [PATCH 1/2] dt-bindings: at24: add ST M24C64-D Additional Write lockable page Marek Vasut
2023-10-13 15:02 ` Conor Dooley
2023-10-16 6:49 ` 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=0120031f-5b08-44ee-b6a1-b2ea38f8c001@denx.de \
--to=marex@denx.de \
--cc=alexander.stein@ew.tq-group.com \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).