[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGb2v650sctP83mdoYtcws2zVzJzfBqq=AvAXYH-WaOoPBDx2Q@mail.gmail.com>
Date: Fri, 27 Dec 2024 23:18:06 +0800
From: Chen-Yu Tsai <wens@...e.org>
To: Parthiban <parthiban@...umiz.com>
Cc: Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>,
Jernej Skrabec <jernej.skrabec@...il.com>, Samuel Holland <samuel@...lland.org>,
Yangtao Li <frank@...winnertech.com>, Maxime Ripard <mripard@...nel.org>,
Rob Herring <robh@...nel.org>, Cody Eksal <masterr3c0rd@...chal.quest>, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-sunxi@...ts.linux.dev,
linux-kernel@...r.kernel.org, Andre Przywara <andre.przywara@....com>,
stable@...r.kernel.org
Subject: Re: [PATCH] clk: sunxi-ng: a100: enable MMC clock reparenting
On Fri, Dec 27, 2024 at 4:45 PM Parthiban <parthiban@...umiz.com> wrote:
>
> On 11/10/24 5:53 PM, Chen-Yu Tsai wrote:
> > On Fri, 08 Nov 2024 20:37:37 -0400, Cody Eksal wrote:
> >> While testing the MMC nodes proposed in [1], it was noted that mmc0/1
> >> would fail to initialize, with "mmc: fatal err update clk timeout" in
> >> the kernel logs. A closer look at the clock definitions showed that the MMC
> >> MPs had the "CLK_SET_RATE_NO_REPARENT" flag set. No reason was given for
> >> adding this flag in the first place, and its original purpose is unknown,
> >> but it doesn't seem to make sense and results in severe limitations to MMC
> >> speeds. Thus, remove this flag from the 3 MMC MPs.
> >>
> >> [...]
> >
> > Applied to clk-for-6.13 in git@...hub.com:linux-sunxi/linux-sunxi.git, thanks!
> >
> > [1/1] clk: sunxi-ng: a100: enable MMC clock reparenting
> > commit: 3fd8177f0015c32fdb0af0feab0bcf344aa74832
> This commit is missing in 6.13-rc4. Will it be merged in the next rcX?
It looks like I tagged the wrong commit when I sent the pull request.
I'll try to send a PR for it as a fix.
ChenYu
Powered by blists - more mailing lists