From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Marek Vasut <marek.vasut@mailbox.org>,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] clk: renesas: cpg-mssr: Read back reset registers to assure values latched
Date: Mon, 22 Sep 2025 15:57:19 +0200 [thread overview]
Message-ID: <aNFVv_n7y-ZmblX-@shikoro> (raw)
In-Reply-To: <CAMuHMdWuCyq+jXSasGdrMOSBP-XmDG-wHsBaXUMTGA3mtq_C5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
> So e.g. MSIOF has synchronized resets, while I2C has not, although
> both are connected to the peripheral AXI bus...
Is this why we need 'read_poll_timeout_atomic' in 'rcar_i2c_do_reset()'
then? I have never received a reason besides "HW engineers said so".
This is pre-Gen4, though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-22 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 3:06 [PATCH] clk: renesas: cpg-mssr: Read back reset registers to assure values latched Marek Vasut
2025-09-18 6:08 ` Wolfram Sang
2025-09-18 13:38 ` Marek Vasut
2025-09-18 11:11 ` Lad, Prabhakar
2025-09-18 13:42 ` Marek Vasut
2025-09-18 15:05 ` Lad, Prabhakar
2025-09-18 23:16 ` Marek Vasut
2025-09-19 8:23 ` Lad, Prabhakar
2025-09-22 11:22 ` Geert Uytterhoeven
2025-09-22 13:57 ` Wolfram Sang [this message]
2025-09-22 14:08 ` Geert Uytterhoeven
2025-09-22 14:23 ` Wolfram Sang
2025-09-19 7:21 ` Geert Uytterhoeven
2025-09-19 8:22 ` Lad, Prabhakar
2025-09-19 12:19 ` Marek Vasut
2025-09-22 6:45 ` 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=aNFVv_n7y-ZmblX-@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut@mailbox.org \
--cc=mturquette@baylibre.com \
--cc=prabhakar.csengg@gmail.com \
--cc=sboyd@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