public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: cnsztl@gmail.com
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	dsimic@manjaro.org, grzegorz@sternicz.uk, heiko@sntech.de,
	jonas@kwiboo.se, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	liujianfeng1994@gmail.com, robh@kernel.org,
	shawn.lin@rock-chips.com
Subject: Re: [PATCH] arm64: dts: rockchip: fix eMMC corruption on NanoPC-T6 with A3A444 chips
Date: Thu, 30 Oct 2025 17:16:49 +0800	[thread overview]
Message-ID: <20251030091649.25396-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <5af928c4-4b6e-489c-ad39-26cef3dd7473@gmail.com>

Hi Tianling,

On Tue, 28 Oct 2025 01:34:25 +0800, Tianling Shen wrote:
>>> May I ask you to test another patch I just posted to see if it fixes
>>> your issue?
>>>
>>> https://patchwork.kernel.org/project/linux-mmc/ 
>>> patch/1760924981-52339-1- git-send-email-shawn.lin@rock-chips.com/
>> 
>> Thank you for the patch! I will ask my friend to test it but he uses 
>> this board as a home router, so it may take a few days or weeks to 
>> report the result.
>
>Hi all, sorry for the late. My friend has tested this patch and it works 
>fine after 50 times dd operation. A big thanks to Shawn!
>
>And hi Jianfeng, I found you made a similiar patch[1] for the ROCK 5 ITX 
>board to lower down the mmc speed, could you please check if this patch 
>also fixes your issue?

I don't have rock 5 itx near my hand to test, but I have another board
ROCK 5B with similar issue. And after applying the patch from Shawn, this
board can run HS400 mode with max freq 200000000.

I will test on rock 5 itx later when I have chance.

Best regards,
Jianfeng

  reply	other threads:[~2025-10-30  9:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  7:39 [PATCH] arm64: dts: rockchip: fix eMMC corruption on NanoPC-T6 with A3A444 chips Tianling Shen
2025-10-17 10:25 ` Dragan Simic
2025-10-17 12:08   ` Tianling Shen
2025-10-17 15:15     ` Dragan Simic
2025-10-17 16:34       ` Tianling Shen
2025-10-17 16:51         ` Dragan Simic
2025-10-18  0:42       ` Jimmy Hon
2025-10-18  8:30         ` Dragan Simic
2025-10-18 12:14           ` Hugh Cole-Baker
2025-10-18 13:57             ` Dragan Simic
2025-10-19 17:25               ` Anand Moon
2025-10-19 18:09                 ` Dragan Simic
2025-10-20  3:13                   ` Anand Moon
     [not found]   ` <CABGV7H_pTkJ_-WQNgVbGE+Ys7jOZaKcRrnMtPr8idfKoYMgKjg@mail.gmail.com>
2025-10-19 17:04     ` Dragan Simic
2025-10-20  1:53 ` Shawn Lin
2025-10-20  4:44   ` Tianling Shen
2025-10-20  8:20     ` Shawn Lin
2025-10-27 17:34     ` Tianling Shen
2025-10-30  9:16       ` Jianfeng Liu [this message]
2025-11-01 11:54       ` Heiko Stuebner
2025-11-01 12:14         ` Tianling Shen
2025-11-01 12:50         ` Dragan Simic
2025-11-05 11:59           ` Anand Moon
  -- strict thread matches above, loose matches on Subject: below --
2025-10-20  9:41 Dragan Simic

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=20251030091649.25396-1-liujianfeng1994@gmail.com \
    --to=liujianfeng1994@gmail.com \
    --cc=cnsztl@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=grzegorz@sternicz.uk \
    --cc=heiko@sntech.de \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    /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