From: Shawn Lin <shawn.lin@rock-chips.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: shawn.lin@rock-chips.com,
"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add mphy reset to ufshc node
Date: Wed, 11 Mar 2026 21:36:26 +0800 [thread overview]
Message-ID: <83c2b26c-cee9-9109-3bb1-e053b72040cc@rock-chips.com> (raw)
In-Reply-To: <20260311-rich-colorful-vicugna-abb4f7@quoll>
在 2026/03/11 星期三 21:11, Krzysztof Kozlowski 写道:
> On Wed, Mar 11, 2026 at 09:40:18AM +0800, Shawn Lin wrote:
>> Add mphy reset to ufshc node to fully reset the whole UFS blocks
>> if needed. Otherwise, it may occasionally prevent the UFS controller
>> from successfully linking up with the device.
>>
>> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>> ---
>>
>
> You must not combine DTS changes with patchset targetting SCSI/UFS,
> because they apply entire set and this DTS CANNOT go there.
>
Well, I was thinking that dt-bingdings will go via UFS tree but DTS is
picked up via rockchip tree. Combine them together is easy for folks to
reviewed. Will send them separately.
> NAK
>
> Best regards,
> Krzysztof
>
>
prev parent reply other threads:[~2026-03-11 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 1:40 [PATCH 0/2] Add mphy reset signal to Rockchip ufshc node Shawn Lin
2026-03-11 1:40 ` [PATCH 1/2] scsi: ufs: drockchip,rk3576-ufshc: dt-bindings: Add new mphy reset item Shawn Lin
2026-03-11 13:10 ` Krzysztof Kozlowski
2026-03-11 13:29 ` Shawn Lin
2026-03-11 13:38 ` Krzysztof Kozlowski
2026-03-11 1:40 ` [PATCH 2/2] arm64: dts: rockchip: Add mphy reset to ufshc node Shawn Lin
2026-03-11 13:11 ` Krzysztof Kozlowski
2026-03-11 13:36 ` 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=83c2b26c-cee9-9109-3bb1-e053b72040cc@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=robh@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