[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14003986.uLZWGnKmhe@workhorse>
Date: Tue, 23 Dec 2025 17:13:39 +0100
From: Nicolas Frattaroli <nicolas.frattaroli@...labora.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>,
"neil.armstrong@...aro.org" <neil.armstrong@...aro.org>,
"conor+dt@...nel.org" <conor+dt@...nel.org>,
Chaotian Jing (井朝天) <Chaotian.Jing@...iatek.com>,
"lgirdwood@...il.com" <lgirdwood@...il.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>,
"broonie@...nel.org" <broonie@...nel.org>,
Peter Wang (王信友) <peter.wang@...iatek.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 v4 07/25] scsi: ufs: mediatek: Rework 0.9V regulator
On Tuesday, 23 December 2025 10:35:39 Central European Standard Time Peter Wang (王信友) wrote:
> On Thu, 2025-12-18 at 13:54 +0100, Nicolas Frattaroli wrote:
> >
> > +static int ufs_mtk_get_supplies(struct ufs_mtk_host *host)
> > +{
> > + struct device *dev = host->hba->dev;
> > + const struct ufs_mtk_soc_data *data =
> > of_device_get_match_data(dev);
> > +
> > + if (!data || !data->has_avdd09)
> > + return 0;
> >
>
>
> Hi Nicolas,
>
> It seems that has_avdd09 is not necessary, because if the
> platform does not support avdd09, it will return an error
> (-ENODEV) and bypass the avdd09 flow, right?
>
> Thanks
> Peter
>
>
>
>
Hi,
that would allow compatibles that are not allowed to have an avdd09
regulator by the binding (because the SoC doesn't have that pin) to
have one specified in the device tree get picked up. This would then
cause those devices with such a device tree to enter
ufs_mtk_va09_pwr_ctrl(), which is not what we want. While we could
blame this on the DT being wrong in that case, I think it's better
if we avoid such a situation entirely.
Kind regards,
Nicolas Frattaroli
Powered by blists - more mailing lists