U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Lukasz Majewski <lukma@denx.de>,
	Ryder Lee <ryder.lee@mediatek.com>,
	Weijie Gao <weijie.gao@mediatek.com>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>,
	Igor Belwon <igor.belwon@mentallysanemainliners.org>,
	Julien Stephan <jstephan@baylibre.com>,
	GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>,
	Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.u-boot-project.org, Sam Shih <Sam.Shih@mediatek.com>
Subject: Re: [PATCH] clk: mediatek: fix reprobe regression
Date: Thu, 13 Aug 2026 08:15:40 -0500	[thread overview]
Message-ID: <a484c17b-83b2-4d10-92f0-554b35b53341@baylibre.com> (raw)
In-Reply-To: <20260813-mtk-clk-fix-reprobe-regression-v1-1-ed259968c2b8@baylibre.com>

On 8/13/26 8:10 AM, David Lechner wrote:
> Clear the MediaTek clock provider registry after relocation. This is
> necessary for a couple of reasons. If any clock probed before the
> relocation, the registry will contain a pointer to pre-relocation
> memory. Also, all drivers reprobe after relocation, so even if we
> had a valid pointer, it would be to a clock provider that had not been
> reprobed yet. Clearing the registry ensures that all clock providers
> are re-registered when they are reprobed after relocation.
> 
Disregard. I forgot an important detail and will send v2 shortly.


  reply	other threads:[~2026-08-13 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 13:10 [PATCH] clk: mediatek: fix reprobe regression David Lechner
2026-08-13 13:15 ` David Lechner [this message]
2026-08-14  3:35 ` sam.shih

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=a484c17b-83b2-4d10-92f0-554b35b53341@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=GSS_MTK_Uboot_upstream@mediatek.com \
    --cc=Sam.Shih@mediatek.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=igor.belwon@mentallysanemainliners.org \
    --cc=jstephan@baylibre.com \
    --cc=lukma@denx.de \
    --cc=ryder.lee@mediatek.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=weijie.gao@mediatek.com \
    /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