From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Peng Fan <peng.fan@nxp.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Tom Rini <trini@konsulko.com>,
Andre Przywara <andre.przywara@arm.com>
Cc: "Simon Glass" <sjg@chromium.org>,
"Kuba Szczodrzyński" <kuba@szczodrzynski.pl>,
"Icenowy Zheng" <icenowy@aosc.io>,
u-boot@lists.denx.de, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH 1/2] sunxi: mmc: Fix T113-s3 MMC clock divider
Date: Wed, 26 Feb 2025 16:54:39 +0100 [thread overview]
Message-ID: <2359168.ElGaqSPkdT@jernej-laptop> (raw)
In-Reply-To: <20250226113712.1257061-2-andre.przywara@arm.com>
Dne sreda, 26. februar 2025 ob 12:37:11 Srednjeevropski standardni čas je Andre Przywara napisal(a):
> On the Allwinner D1/R528/T113-s3 SoCs the MMC clock source selected by
> mux value 1 is PLL_PERIPH0(1x), not (2x), as in the other SoCs.
> But we have still the hidden divisor of 2 in the MMC mod clock, so
> need to explicitly compensate for that on those SoCs.
>
> This leads to the actually programmed clock rate to be double compared
> to before, which increases the MMC performance on those SoCs.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> Reported-by: Kuba Szczodrzyński <kuba@szczodrzynski.pl>
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
next prev parent reply other threads:[~2025-02-26 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 11:37 [PATCH 0/2] sunxi: clk/mmc: Fix T113-s3 MMC performance Andre Przywara
2025-02-26 11:37 ` [PATCH 1/2] sunxi: mmc: Fix T113-s3 MMC clock divider Andre Przywara
2025-02-26 15:54 ` Jernej Škrabec [this message]
2025-02-27 0:31 ` Peng Fan
2025-02-27 2:23 ` Tom Rini
2025-02-27 2:25 ` Peng Fan
2025-02-26 11:37 ` [PATCH 2/2] sunxi: sun50i_h6: clock: fix PLL_PERIPH0 rate calculation Andre Przywara
2025-02-26 15:54 ` Jernej Škrabec
2025-02-27 0:33 ` Peng Fan
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=2359168.ElGaqSPkdT@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=andre.przywara@arm.com \
--cc=icenowy@aosc.io \
--cc=jh80.chung@samsung.com \
--cc=kuba@szczodrzynski.pl \
--cc=linux-sunxi@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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