From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux I2C <linux-i2c@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] i2c: rcar: Add R-Car Gen4 support
Date: Tue, 8 Feb 2022 15:43:31 +0100 [thread overview]
Message-ID: <YgKBk5o2aFegPNI1@ninjato> (raw)
In-Reply-To: <CAMuHMdWNUC+XqMLjY22L6XZ5NTyWTGA6HLruZUNFWBDEpcsmGg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
> Don't we want to introduce a family-specific compatible value for
> R-Car Gen4? At least the SCSS seems to be a new R-Car Gen4 feature
> common to R-Car S4 and R-Car V3U (yes, the latter is advertised as
> the first member of the R-Car Gen4 family, so I intend to move it
> over to renesas,rcar-gen4-* where it makes sense).
Yeah, sure we want the family compatible. But for now it can point to
I2C_RCAR_GEN3, so the patch can stay as is. That is what I was wondering
about why a v2 was needed. If we add SCSS, we can update the family
compatible data for Gen4 to I2C_RCAR_GEN4. Unless I miss something.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-08 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 14:33 [PATCH 0/2] i2c: rcar: Add R-Car S4-8 support Geert Uytterhoeven
2022-02-03 14:33 ` [PATCH 1/2] dt-bindings: i2c: renesas,rcar-i2c: Add r8a779f0 support Geert Uytterhoeven
2022-02-10 22:15 ` Wolfram Sang
2022-02-11 14:11 ` Rob Herring
2022-02-11 17:33 ` Wolfram Sang
2022-02-03 14:33 ` [PATCH 2/2] i2c: rcar: Add R-Car Gen4 support Geert Uytterhoeven
2022-02-08 8:08 ` Geert Uytterhoeven
2022-02-08 12:35 ` Wolfram Sang
2022-02-08 14:30 ` Geert Uytterhoeven
2022-02-08 14:43 ` Wolfram Sang [this message]
2022-02-08 14:50 ` Geert Uytterhoeven
2022-02-10 22:16 ` Wolfram Sang
2022-02-11 17:33 ` Wolfram Sang
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=YgKBk5o2aFegPNI1@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.