From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/5] ARM: dts: renesas: r9a06g032-rzn1d400-db: describe I2C bus
Date: Sat, 29 Mar 2025 10:37:46 +0100 [thread overview]
Message-ID: <Z-e_auJxLrg1d69I@shikoro> (raw)
In-Reply-To: <f15da9fc-781d-440f-ac36-f19f96146433@omp.ru>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
> [...]> + /* Some revisions may have a 24cs64 at address 0x58 */
> > + eeprom@50 {
>
> So 0x58 or 0x50?
The eeprom is at 0x50, always. The serial ID (the cs-part) is at 0x58.
This is always the case for cs-eeproms, see their existing usage in DT.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-03-29 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 15:31 [PATCH 0/5] ARM: dts: renesas: r9a06g032-rzn1d400-db: enable I2C infrastructure Wolfram Sang
2025-03-28 15:31 ` [PATCH 1/5] ARM: dts: renesas: r9a06g032: Describe I2C controllers Wolfram Sang
2025-04-11 7:18 ` Geert Uytterhoeven
2025-03-28 15:31 ` [PATCH 2/5] ARM: dts: renesas: r9a06g032-rzn1d400-db: describe I2C bus Wolfram Sang
2025-03-29 9:13 ` Sergey Shtylyov
2025-03-29 9:37 ` Wolfram Sang [this message]
2025-04-11 7:35 ` Geert Uytterhoeven
2025-03-28 15:31 ` [PATCH 3/5] ARM: dts: renesas: r9a06g032-rzn1d400-eb: " Wolfram Sang
2025-04-11 9:22 ` Geert Uytterhoeven
2025-03-28 15:31 ` [PATCH 4/5] ARM: dts: renesas: r9a06g032-rzn1d400-db: describe LEDs Wolfram Sang
2025-04-11 8:59 ` Geert Uytterhoeven
2025-04-11 11:40 ` Wolfram Sang
2025-04-14 13:41 ` Geert Uytterhoeven
2025-03-28 15:31 ` [PATCH 5/5] ARM: dts: renesas: r9a06g032-rzn1d400-db: describe keys Wolfram Sang
2025-04-11 9:02 ` Geert Uytterhoeven
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=Z-e_auJxLrg1d69I@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=s.shtylyov@omp.ru \
/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).