From: Parthiban <parthiban@linumiz.com>
To: Chen-Yu Tsai <wens@csie.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Yangtao Li <frank@allwinnertech.com>,
Maxime Ripard <mripard@kernel.org>, Rob Herring <robh@kernel.org>,
Cody Eksal <masterr3c0rd@epochal.quest>
Cc: parthiban@linumiz.com, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] clk: sunxi-ng: a100: enable MMC clock reparenting
Date: Fri, 27 Dec 2024 14:14:59 +0530 [thread overview]
Message-ID: <9415ca9c-f303-4507-8cd6-cb08ee09e988@linumiz.com> (raw)
In-Reply-To: <173124139852.3585539.10704015898700065278.b4-ty@csie.org>
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@github.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?
Thanks,
Parthiban
>
> Best regards,
next prev parent reply other threads:[~2024-12-27 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 0:37 [PATCH] clk: sunxi-ng: a100: enable MMC clock reparenting Cody Eksal
2024-11-09 16:02 ` Chen-Yu Tsai
2024-11-09 17:17 ` Cody Eksal
2024-11-10 12:23 ` Chen-Yu Tsai
2024-12-27 8:44 ` Parthiban [this message]
2024-12-27 15:18 ` Chen-Yu Tsai
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=9415ca9c-f303-4507-8cd6-cb08ee09e988@linumiz.com \
--to=parthiban@linumiz.com \
--cc=andre.przywara@arm.com \
--cc=frank@allwinnertech.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=masterr3c0rd@epochal.quest \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wens@csie.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