Devicetree
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>, Ulf Hansson <ulf.hansson@linaro.org>
Cc: shawn.lin@rock-chips.com, linux-rockchip@lists.infradead.org,
	linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	FUKAUMI Naoki <naoki@radxa.com>,
	Marco Schirrmeister <mschirrmeister@gmail.com>,
	John Clark <inindev@gmail.com>, Tianling Shen <cnsztl@gmail.com>,
	Detlev Casanova <detlev.casanova@collabora.com>
Subject: Re: (subset) [PATCH v4 0/5] Fix sd card support for RK3576 platform
Date: Fri, 16 Jan 2026 22:24:38 +0800	[thread overview]
Message-ID: <0c6b4cc1-ce99-4d59-a470-b07dec763e8b@rock-chips.com> (raw)
In-Reply-To: <176857210194.116631.11189192556414524729.b4-ty@sntech.de>


在 2026/01/16 星期五 22:04, Heiko Stuebner 写道:
> 
> On Fri, 16 Jan 2026 08:55:27 +0800, Shawn Lin wrote:
>> Marco reported a problem[1] for his FriendlyElec NanoPi R76S board. The problem
>> is becuase after runtime suspend, the associated power domain is powered off, which
>> resets the registers including power control bit, card detection logic and internal
>> phase registers. This leads to three problems need to be solved.
>>
>> 1. hot-plug broken:
>>
>> [...]
> 
> Applied, thanks!
> 
> [1/5] soc: rockchip: grf: Fix wrong RK3576_IOCGRF_MISC_CON definition
>        commit: 3cdc30c42d4a87444f6c7afbefd6a9381c4caa27
> [2/5] soc: rockchip: grf: Support multiple grf to be handled
>        commit: 75fb63ae031211e9264ac888fabc2ca9cd3fcccf
> [4/5] arm64: dts: rockchip: Fix SD card support for RK3576 EVB1
>        commit: 7226664bf952c4cfddccd74b154a7d994608d153
> [5/5] arm64: dts: rockchip: Fix SD card support for RK3576 Nanopi R76s
>        commit: a9c1acebfe0484343a443d082e039ca77186ed22
> 
> I've queued them for 6.20 because I'd like them to marinate a bit longer
> due to the size of the changes, but added Cc-stable tags so that they
> then can make their way into stable kernels.
> 

Sure, thanks Heiko.

> Depending if MMC maintainers see patch3, you might want to resend it
> individually at some point.
> 
> 
> Best regards,


      reply	other threads:[~2026-01-16 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16  0:55 [PATCH v4 0/5] Fix sd card support for RK3576 platform Shawn Lin
2026-01-16  0:55 ` [PATCH v4 1/5] soc: rockchip: grf: Fix wrong RK3576_IOCGRF_MISC_CON definition Shawn Lin
2026-01-16  0:55 ` [PATCH v4 2/5] soc: rockchip: grf: Support multiple grf to be handled Shawn Lin
2026-01-16  0:55 ` [PATCH v4 3/5] mmc: dw_mmc-rockchip: Fix runtime PM support for internal phase support Shawn Lin
2026-01-16 10:28   ` Heiko Stübner
2026-01-21 14:54   ` Ulf Hansson
2026-01-16  0:55 ` [PATCH v4 4/5] arm64: dts: rockchip: Fix SD card support for RK3576 EVB1 Shawn Lin
2026-01-16  0:55 ` [PATCH v4 5/5] arm64: dts: rockchip: Fix SD card support for RK3576 Nanopi R76s Shawn Lin
2026-01-16 14:04 ` (subset) [PATCH v4 0/5] Fix sd card support for RK3576 platform Heiko Stuebner
2026-01-16 14:24   ` Shawn Lin [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=0c6b4cc1-ce99-4d59-a470-b07dec763e8b@rock-chips.com \
    --to=shawn.lin@rock-chips.com \
    --cc=cnsztl@gmail.com \
    --cc=detlev.casanova@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=inindev@gmail.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mschirrmeister@gmail.com \
    --cc=naoki@radxa.com \
    --cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox