From: "Heiko Stübner" <heiko@sntech.de>
To: Quentin Schulz <quentin.schulz@cherry.de>,
Alexey Charkov <alchark@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Manivannan Sadhasivam <mani@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: Explicitly request UFS reset pin on RK3576
Date: Tue, 20 Jan 2026 15:41:06 +0100 [thread overview]
Message-ID: <4830042.taCxCBeP46@diego> (raw)
In-Reply-To: <CABjd4YwAMbH21jcjhks7ThoXzcF8GeOzBPYDvN+7cip0iA6stg@mail.gmail.com>
Am Dienstag, 20. Januar 2026, 14:14:48 Mitteleuropäische Normalzeit schrieb Alexey Charkov:
> On Tue, Jan 20, 2026 at 5:00 PM Quentin Schulz <quentin.schulz@cherry.de> wrote:
> >
> > Hi Alexey,
> >
> > On 1/20/26 1:53 PM, Alexey Charkov wrote:
> > > Rockchip RK3576 UFS controller uses a dedicated pin to reset the connected
> > > UFS device, which can operate either in a hardware controlled mode or as a
> > > GPIO pin.
> > >
> > > Power-on default is GPIO mode, but the boot ROM reconfigures it to a
> > > hardware controlled mode if it uses UFS to load the next boot stage.
> > >
> > > Given that existing bindings (and rk3576.dtsi) expect a GPIO-controlled
> > > device reset, request the required pin config explicitly.
> > >
> > > This doesn't appear to affect Linux, but it does affect U-boot:
> > >
> > > Before:
> > > => md.l 0x2604b398
> > > 2604b398: 00000011 00000000 00000000 00000000 ................
> > > < ... snip ... >
> > > => ufs init
> > > ufshcd-rockchip ufshc@2a2d0000: [RX, TX]: gear=[3, 3], lane[2, 2], pwr[FASTAUTO_MODE, FASTAUTO_MODE], rate = 2
> > > => md.l 0x2604b398
> > > 2604b398: 00000011 00000000 00000000 00000000 ................
> > >
> > > After:
> > > => md.l 0x2604b398
> > > 2604b398: 00000011 00000000 00000000 00000000 ................
> > > < ... snip ...>
> > > => ufs init
> > > ufshcd-rockchip ufshc@2a2d0000: [RX, TX]: gear=[3, 3], lane[2, 2], pwr[FASTAUTO_MODE, FASTAUTO_MODE], rate = 2
> > > => md.l 0x2604b398
> > > 2604b398: 00000010 00000000 00000000 00000000 ................
> > >
> > > (0x2604b398 is the respective pin mux register, with its BIT0 driving the
> > > mode of UFS_RST: unset = GPIO, set = hardware controlled UFS_RST)
> > >
> > > This helps ensure that GPIO-driven device reset actually fires when the
> > > system requests it, not when whatever black box magic inside the UFSHC
> > > decides to reset the flash chip.
> > >
> >
> > Would have liked a mention on why pull-down in the commit log.
>
> Indeed. Heiko, if you're going to apply this to your tree, would you
> mind amending the commit description with something like the
> following?
>
> The pin is requested with pull-down enabled, which is in line with the
> SoC power-on default and helps ensure that the attached UFS chip stays
> in reset until the driver takes over the control of the respective
> GPIO line.
Will do :-)
Heiko
> > In any case,
> >
> > Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> Thanks a lot!
>
> Best regards,
> Alexey
>
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Quentin Schulz <quentin.schulz@cherry.de>,
Alexey Charkov <alchark@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Shawn Lin <shawn.lin@rock-chips.com>,
Manivannan Sadhasivam <mani@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: Explicitly request UFS reset pin on RK3576
Date: Tue, 20 Jan 2026 15:41:06 +0100 [thread overview]
Message-ID: <4830042.taCxCBeP46@diego> (raw)
In-Reply-To: <CABjd4YwAMbH21jcjhks7ThoXzcF8GeOzBPYDvN+7cip0iA6stg@mail.gmail.com>
Am Dienstag, 20. Januar 2026, 14:14:48 Mitteleuropäische Normalzeit schrieb Alexey Charkov:
> On Tue, Jan 20, 2026 at 5:00 PM Quentin Schulz <quentin.schulz@cherry.de> wrote:
> >
> > Hi Alexey,
> >
> > On 1/20/26 1:53 PM, Alexey Charkov wrote:
> > > Rockchip RK3576 UFS controller uses a dedicated pin to reset the connected
> > > UFS device, which can operate either in a hardware controlled mode or as a
> > > GPIO pin.
> > >
> > > Power-on default is GPIO mode, but the boot ROM reconfigures it to a
> > > hardware controlled mode if it uses UFS to load the next boot stage.
> > >
> > > Given that existing bindings (and rk3576.dtsi) expect a GPIO-controlled
> > > device reset, request the required pin config explicitly.
> > >
> > > This doesn't appear to affect Linux, but it does affect U-boot:
> > >
> > > Before:
> > > => md.l 0x2604b398
> > > 2604b398: 00000011 00000000 00000000 00000000 ................
> > > < ... snip ... >
> > > => ufs init
> > > ufshcd-rockchip ufshc@2a2d0000: [RX, TX]: gear=[3, 3], lane[2, 2], pwr[FASTAUTO_MODE, FASTAUTO_MODE], rate = 2
> > > => md.l 0x2604b398
> > > 2604b398: 00000011 00000000 00000000 00000000 ................
> > >
> > > After:
> > > => md.l 0x2604b398
> > > 2604b398: 00000011 00000000 00000000 00000000 ................
> > > < ... snip ...>
> > > => ufs init
> > > ufshcd-rockchip ufshc@2a2d0000: [RX, TX]: gear=[3, 3], lane[2, 2], pwr[FASTAUTO_MODE, FASTAUTO_MODE], rate = 2
> > > => md.l 0x2604b398
> > > 2604b398: 00000010 00000000 00000000 00000000 ................
> > >
> > > (0x2604b398 is the respective pin mux register, with its BIT0 driving the
> > > mode of UFS_RST: unset = GPIO, set = hardware controlled UFS_RST)
> > >
> > > This helps ensure that GPIO-driven device reset actually fires when the
> > > system requests it, not when whatever black box magic inside the UFSHC
> > > decides to reset the flash chip.
> > >
> >
> > Would have liked a mention on why pull-down in the commit log.
>
> Indeed. Heiko, if you're going to apply this to your tree, would you
> mind amending the commit description with something like the
> following?
>
> The pin is requested with pull-down enabled, which is in line with the
> SoC power-on default and helps ensure that the attached UFS chip stays
> in reset until the driver takes over the control of the respective
> GPIO line.
Will do :-)
Heiko
> > In any case,
> >
> > Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> Thanks a lot!
>
> Best regards,
> Alexey
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-01-20 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:53 [PATCH v2] arm64: dts: rockchip: Explicitly request UFS reset pin on RK3576 Alexey Charkov
2026-01-20 12:53 ` Alexey Charkov
2026-01-20 12:59 ` Quentin Schulz
2026-01-20 12:59 ` Quentin Schulz
2026-01-20 13:14 ` Alexey Charkov
2026-01-20 13:14 ` Alexey Charkov
2026-01-20 14:41 ` Heiko Stübner [this message]
2026-01-20 14:41 ` Heiko Stübner
2026-01-20 21:45 ` Rob Herring
2026-01-20 21:45 ` Rob Herring
2026-01-21 7:35 ` Alexey Charkov
2026-01-21 7:35 ` Alexey Charkov
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=4830042.taCxCBeP46@diego \
--to=heiko@sntech.de \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=stable@vger.kernel.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.