lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <AM7P189MB100973D1DC0164099067E2AEE3C52@AM7P189MB1009.EURP189.PROD.OUTLOOK.COM>
Date: Wed, 19 Feb 2025 16:05:55 +0100
From: Maud Spierings <maud_spierings@...mail.com>
To: Emil Renner Berthing <emil.renner.berthing@...onical.com>,
 Maud Spierings via B4 Relay <devnull+maud_spierings.hotmail.com@...nel.org>,
 Conor Dooley <conor@...nel.org>, Emil Renner Berthing <kernel@...il.dk>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt
 <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
 Alexandre Ghiti <alex@...ti.fr>
Cc: linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: dts: starfive: fml13v01: increase eMMC bus speed

On 2/19/25 3:21 PM, Emil Renner Berthing wrote:
> Maud Spierings via B4 Relay wrote:
>> From: Maud Spierings <maud_spierings@...mail.com>
>>
>> The assigned clock speed of 50 MHz is and max-frequency of 100MHz are
>> limitting this interface which is SDIO 5.0 capable. Sadly at 200MHz it
>> fails to mount an eMMC drive, 150MHz (really 132 MHz) is the highest it
>> was able to get.
>>
>> This improves the seq read/write performance by 2x~
>>
>> Signed-off-by: Maud Spierings <maud_spierings@...mail.com>
>> ---
>> I put this in this specific dts instead of the common one as I cannot
>> test if other boards are also able to handle these speeds.
> Hi Maud,
>
> Thanks for the patch!
>
> These settings work on my Milk-V Mars board booting off eMMC, but I'm not sure
> if that means we can just raise the frequency across all the JH7110 boards.
> The eMMC on my Milk-V mars is a detachable module that identifies as
>
>    mmcblk0: mmc0:0001 DG4016 14.7 GiB
>
> I guess what works might depend on the module too. Is the eMMC on the framework
> board soldered on?


No it is also a detachable module, it supports the same interface as 
most eMMC modules seem to.

> Raising the max-frequency to 200MHz seems right for all boards since we're
> already saying mmc0 supports HS200 mode.
>
> Maybe we could begin by raising the max frequency to 200MHz for all boards,
> but only assign the 150MHz rate on the framework board?

That seems alright with me, I'll send a v2 with max-frequency adjusted 
in jh7110-common instead.

> /Emil
kind regards,
Maud

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ