All of lore.kernel.org
 help / color / mirror / Atom feed
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 16:23:37 +0200	[thread overview]
Message-ID: <aNFb6S1WApJl-k45@shikoro> (raw)
In-Reply-To: <CAMuHMdV7QvQFs_wXYy5B8fyO_TT2-ksHtfRKQXrhe3ouQpJALg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 270 bytes --]


> Can you trigger an issue by removing the polling, and does Marek's
> patch fix it?

IIRC not with I2C, but SHDI needs this as well and there it surely
happened during development a few years ago. I need to work on SDHI soon
anyhow, I will see if I can reproduce it.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-09-22 14:23 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
2025-09-22 14:08             ` Geert Uytterhoeven
2025-09-22 14:23               ` Wolfram Sang [this message]
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=aNFb6S1WApJl-k45@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 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.