From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-renesas-soc@vger.kernel.org,
Andi Shyti <andi.shyti@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 2/2] i2c: rcar: add R-Car Gen5 support
Date: Mon, 17 Aug 2026 09:42:08 +0200 [thread overview]
Message-ID: <aoK7UBuJHiXfYHNI@ninjato> (raw)
In-Reply-To: <CAMuHMdWVtfizYD4vKzsQrVpzr4ekmFQRtDZ4QpOhVHMh6K7JjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
> This could indeed be moved into the reset driver. However, that
> means the reset driver needs to become aware of the peculiarities
> of the various target devices on the various SoCs. We already have
> something similar for module stop delays on RZ/V2H, though.
> And it means more dependencies to track when adding driver support.
>
> Then there's still the user in the PCIe driver[2], which can't be
> handled like that.
I can see the argument that the extra code could live in the reset
handler. But given the harder dependency tracking plus the inability to
handle all corner cases in the reset driver anyhow, I tend to update the
handling in this I2C driver.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-08-17 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 12:25 [PATCH v2 0/2] i2c: rcar: add Gen5 support Wolfram Sang
2026-07-27 12:25 ` [PATCH v2 1/2] dt-bindings: i2c: rcar-i2c: Document R-Car X5H support Wolfram Sang
2026-07-27 12:25 ` [PATCH v2 2/2] i2c: rcar: add R-Car Gen5 support Wolfram Sang
2026-08-03 13:14 ` Geert Uytterhoeven
2026-08-03 17:17 ` Wolfram Sang
2026-08-06 8:18 ` Philipp Zabel
2026-08-06 9:09 ` Geert Uytterhoeven
2026-08-17 7:42 ` Wolfram Sang [this message]
2026-07-29 20:35 ` [PATCH v2 0/2] i2c: rcar: add " Andi Shyti
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=aoK7UBuJHiXfYHNI@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=p.zabel@pengutronix.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 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.