public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <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] arm64: dts: rockchip: Explicitly request UFS reset pin on RK3576
Date: Tue, 20 Jan 2026 10:21:01 +0100	[thread overview]
Message-ID: <40619400.XM6RcZxFsP@phil> (raw)
In-Reply-To: <8960787.MhkbZ0Pkbq@diego>

Am Montag, 19. Januar 2026, 15:42:23 Mitteleuropäische Normalzeit schrieb Heiko Stübner:
> Am Montag, 19. Januar 2026, 15:05:16 Mitteleuropäische Normalzeit schrieb Alexey Charkov:
> > Happy to make a v2 with an explicit pull-down. Will wait a bit for any
> > other potential feedback though.
> 
> I'd side with Quentin here, having the pin firmly on one state, when no-one
> (board nor driver) is caring would be my preference.
> Especially as Quentin said, this is the hardware-default too.

Also it would be good to send that v2 sooner rather than later, as we're
pretty late in the current development cycle already.
(We're after -rc6 already)


Thanks
Heiko



  reply	other threads:[~2026-01-20  9:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19  9:22 [PATCH] arm64: dts: rockchip: Explicitly request UFS reset pin on RK3576 Alexey Charkov
2026-01-19 11:08 ` Quentin Schulz
2026-01-19 13:43   ` Alexey Charkov
2026-01-19 13:58     ` Quentin Schulz
2026-01-19 14:05       ` Alexey Charkov
2026-01-19 14:42         ` Heiko Stübner
2026-01-20  9:21           ` Heiko Stuebner [this message]
2026-01-20  1:39 ` Shawn Lin
2026-01-20  7:13   ` Alexey Charkov
2026-01-20  8:55   ` Heiko Stuebner
2026-01-20 10:21     ` Quentin Schulz
2026-01-20 10:26       ` Heiko Stuebner

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=40619400.XM6RcZxFsP@phil \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox