[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74453fd50969b6ad8ad5c11ff842155cb9c29c87.camel@mediatek.com>
Date: Fri, 17 Oct 2025 06:53:45 +0000
From: Peter Wang (王信友) <peter.wang@...iatek.com>
To: "chu.stanley@...il.com" <chu.stanley@...il.com>, "robh@...nel.org"
<robh@...nel.org>, Chunfeng Yun (云春峰)
<Chunfeng.Yun@...iatek.com>, "kishon@...nel.org" <kishon@...nel.org>,
"James.Bottomley@...senPartnership.com"
<James.Bottomley@...senPartnership.com>, "bvanassche@....org"
<bvanassche@....org>, AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>, "conor+dt@...nel.org"
<conor+dt@...nel.org>, "nicolas.frattaroli@...labora.com"
<nicolas.frattaroli@...labora.com>, "vkoul@...nel.org" <vkoul@...nel.org>,
"krzk+dt@...nel.org" <krzk+dt@...nel.org>, "p.zabel@...gutronix.de"
<p.zabel@...gutronix.de>, "alim.akhtar@...sung.com"
<alim.akhtar@...sung.com>, "matthias.bgg@...il.com" <matthias.bgg@...il.com>,
"avri.altman@....com" <avri.altman@....com>, "martin.petersen@...cle.com"
<martin.petersen@...cle.com>
CC: "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-phy@...ts.infradead.org"
<linux-phy@...ts.infradead.org>, "linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>, Louis-Alexis Eyraud
<louisalexis.eyraud@...labora.com>, "kernel@...labora.com"
<kernel@...labora.com>
Subject: Re: [PATCH v2 4/5] phy: mediatek: ufs: Add support for resets
On Thu, 2025-10-16 at 14:06 +0200, Nicolas Frattaroli wrote
>
> The MediaTek UFS PHY supports PHY resets. Until now, they've been
> implemented in the UFS host driver. Since they were never documented
> in
> the UFS HCI node's DT bindings, and no mainline DT uses it, it's fine
> if
> it's moved to the correct location, which is the PHY driver.
>
> Implement the MPHY reset logic in this driver and expose it through
> the
> phy subsystem's reset op. The reset itself is optional, as judging by
> other mainline devices that use this hardware, it's not required for
> the
> device to function.
>
> If no reset is present, the reset op returns -EOPNOTSUPP, which means
> that the ufshci driver can detect it's present and not double sleep
> in
> its own reset function, where it will call the phy reset.
>
> Reviewed-by: Philipp Zabel <p.zabel@...gutronix.de>
> Reviewed-by: AngeloGioacchino Del Regno
> <angelogioacchino.delregno@...labora.com>
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@...labora.com>
Reviewed-by: Peter Wang <peter.wang@...iatek.com>
Powered by blists - more mailing lists