[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230427162251.518a956ce7a9dcd88352725a@hugovil.com>
Date: Thu, 27 Apr 2023 16:22:51 -0400
From: Hugo Villeneuve <hugo@...ovil.com>
To: Fabio Estevam <festevam@...il.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
Hugo Villeneuve <hvilleneuve@...onoff.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] imx8mn-var-som: dts: fix PHY detection bug by adding
deassert delay
On Thu, 27 Apr 2023 17:07:59 -0300
Fabio Estevam <festevam@...il.com> wrote:
> On Thu, Apr 27, 2023 at 5:06 PM Hugo Villeneuve <hugo@...ovil.com> wrote:
>
> > Hi Fabio,
> > it uses a ADIN1300 PHY.
> >
> > The datasheet indicate that the "Management interface active (t4)" state is reached at most 5ms after the reset signal is deasserted.
>
> Please add this information to the commit log and please add a Fixes: tag.
>
> Thanks
Hi,
I am trying to properly add a "Fixes: " tag, but the description for this tag indicates that it is to report that "the patch fixes an issue in a previous commit".
In this case, I cannot identify a commit that introduced that bug, apart from the initial commit of the DTS file which didn't have the reset property present?
Thank you,
Hugo.
--
Hugo Villeneuve <hugo@...ovil.com>
Powered by blists - more mailing lists