From: Andrei Lalaev <andrey.lalaev@gmail.com>
To: Hiago De Franco <hfranco@baylibre.com>
Cc: u-boot@lists.denx.de, u-boot@lists.u-boot-project.org
Subject: Re: [PATCH v2 0/2] board: sophgo: add support for Milk-V Duo 256M
Date: Sat, 5 Sep 2026 15:34:05 +0200 [thread overview]
Message-ID: <d7eea776-10b6-46ff-89ff-19d7e25894e1@gmail.com> (raw)
In-Reply-To: <apsphFWUeaW6MpJF@hiagonb>
Hi Hiago,
On 04.09.26 22:29, Hiago De Franco wrote:
> Hi Andrei,
>
> On Sun, Aug 30, 2026 at 05:29:59PM +0200, Andrei Lalaev wrote:
>> Hi Hiago,
>>
>> So, I've dumped the registers using downstream U-Boot and yes, Claude was right.
>> By default, downstream driver configures the PHY, so the PHY registers
>> have the following values:
>>
>> # PHY_TX_RX_DLY
>> milkv_duo_256m# md.l 0x04310240 1
>> 04310240: 01000100 ....
>>
>> # PHY_CONFIG
>> milkv_duo_256m# md.l 0x0431024c 1
>> 0431024c: 00000001 ....
>>
>>
>> With upstream U-Boot, the same registers are always 0.
>>
>> Simply setting `PHY_TX_RX_DLY` to `0x01000100` is enough to get
>> the SD card working.
>>
>> The attached patch contains the backported PHY configuration from the downstream
>> driver & upstream kernel. Could you please take a look and check if it
>> resolves the issue on your side when increasing the clock?
>
> First, apologies for the delay on my answer, it was a busy week.
>
> I tested your patch and it works fine ;)
> Thanks for the fix. Would you mind sending this patch to u-boot ML?
Sure, I will do it over the next few days. Thank you for your help and testing :)
--
Best regards,
Andrei Lalaev
prev parent reply other threads:[~2026-09-06 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 14:44 [PATCH v2 0/2] board: sophgo: add support for Milk-V Duo 256M Hiago De Franco
2026-07-23 14:44 ` [PATCH v2 1/2] board: sophgo: move ethernet driver to common directory Hiago De Franco
2026-08-05 15:29 ` Leo Liang via U-Boot
2026-07-23 14:44 ` [PATCH v2 2/2] board: sophgo: add support for Milk-V Duo 256M Hiago De Franco
2026-08-05 15:31 ` Leo Liang via U-Boot
2026-08-05 15:50 ` [PATCH v2 0/2] " Leo Liang via U-Boot
2026-08-22 9:15 ` Andrei Lalaev
2026-08-25 12:24 ` Hiago De Franco
2026-08-25 18:01 ` Andrei Lalaev
2026-08-27 13:30 ` Hiago De Franco
2026-08-27 16:04 ` Andrei Lalaev
2026-08-30 15:29 ` Andrei Lalaev
2026-09-04 20:29 ` Hiago De Franco
2026-09-05 13:34 ` Andrei Lalaev [this message]
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=d7eea776-10b6-46ff-89ff-19d7e25894e1@gmail.com \
--to=andrey.lalaev@gmail.com \
--cc=hfranco@baylibre.com \
--cc=u-boot@lists.denx.de \
--cc=u-boot@lists.u-boot-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.