mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Ahmad Fatoum" <a.fatoum@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>,
	"Claude Opus 4.7" <noreply@anthropic.com>,
	Sascha Hauer <sascha@saschahauer.de>
Subject: Re: [PATCH 0/6] mci: rockchip-dwcmshc: add HS200 support
Date: Thu, 07 May 2026 08:03:07 +0000	[thread overview]
Message-ID: <E1wKthL-00000005iSp-239c@pty.whiteo.stw.pengutronix.de> (raw)
In-Reply-To: 79ed02bc-045d-4e0b-a1a4-0158787cb39c@pengutronix.de

On 2026-05-07 09:47, Ahmad Fatoum wrote:
> Hi,
> 
> On 5/7/26 9:02 AM, Sascha Hauer wrote:
> > At least on RK3588 the dwcmshc core doesn't have an internal clock
> > divider, we fully rely on the clock tree to configure the MMC clock.
> > By default the clock comes from the 24MHz oscillator. For higher MMC
> > clocks we have to reparent to a PLL clock, but if we do this once the
> > 6bit divider iss not enough to scale down to the 400kHz MMC
> > initialization clock. This means we must dynamically reparent the clock.
> > This series adds support for finding the best divider/mux combination
> > for composite clocks.
> > 
> > This series also adds some fixes to the dwcmshc driver which used to
> > timeout on writing sometimes.
> 
> \o/
> 
> How much faster was the reading now in your testing?

I now reach 120MB/s compared to 20MB/s before.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



             reply	other threads:[~2026-05-07  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07  8:03 Sascha Hauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-07  7:02 Sascha Hauer
2026-05-07  7:47 ` Ahmad Fatoum

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=E1wKthL-00000005iSp-239c@pty.whiteo.stw.pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=noreply@anthropic.com \
    --cc=sascha@saschahauer.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