| 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
| ||
|
Message-ID: <ccd8be6a-c8d4-407b-906a-e4788a365775@kwiboo.se> Date: Thu, 6 Mar 2025 10:16:00 +0100 From: Jonas Karlman <jonas@...boo.se> To: Chukun Pan <amadeus@....edu.cn> Cc: conor+dt@...nel.org, devicetree@...r.kernel.org, heiko@...ech.de, krzk+dt@...nel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org, linux-rockchip@...ts.infradead.org Subject: Re: [PATCH 0/3] rockchip: Add support for onboard eMMC on Radxa E20C Hi Chukun, On 2025-03-06 10:00, Chukun Pan wrote: > Hi, > >> Driver changes to use different delay and tap num is needed to be able >> to support HS400 modes, something for a future series. With this HS200 >> mode should work: > > I have tried HS200 mode on other rk3528 boards and it works fine, > so can we enable HS200 mode for Radxa E20C first? The host controller already report the HS200 mode, and as shown in cover letter HS200 mode is being enabled/used with this series. However, the driver must use different tap/delay num for HS400(ES) modes. At top of [1] there is a commit that changes to use same tap/delay num as vendor kernel and what I have tested worked in U-Boot. That commit needs to be re-worked before it is ready. Also see [2] for pending work before I plan to complete before moving on to the dwcmshc driver. [1] https://github.com/Kwiboo/linux-rockchip/commits/next-20250227-rk3528-rk3506/ [2] https://github.com/Kwiboo/linux-rockchip/commits/next-20250305-rk3528/ Regards, Jonas > > Thanks, > Chukun >
Powered by blists - more mailing lists