[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJq09z73Ok=np6Lz+WHcWr2KhN4tq1f9O8W4+VR0SZcwAUOb-Q@mail.gmail.com>
Date: Sun, 13 Feb 2022 19:28:56 -0300
From: Luiz Angelo Daros de Luca <luizluca@...il.com>
To: Alvin Šipraga <ALSI@...g-olufsen.dk>
Cc: Arınç ÜNAL <arinc.unal@...nc9.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"andrew@...n.ch" <andrew@...n.ch>,
"vivien.didelot@...il.com" <vivien.didelot@...il.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"olteanv@...il.com" <olteanv@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
Frank Wunderlich <frank-w@...lic-files.de>
Subject: Re: [PATCH net-next v2] net: dsa: realtek: realtek-mdio: reset before setup
> > If realtek-smi also resets before setup with this patch (I don’t understand code very well) can you mention it next to mdio in the summary too?
>
> realtek-smi was already asserting reset. I just asked Luiz to send a
> patch to only try the reset if reset-gpio is actually specified, else it
> prints "asserting RESET" without actually doing it. So this is largely
> cosmetic. But it is odd to touch realtek-smi when the subject is
> realtek-mdio.
>
> Arguably this could be separated into a few patches; something to
> consider if you decide to send a v3 per Florian's comment:
>
> 1. realtek-smi: add if block around reset-gpio assertion
> 2. realtek-smi: demote dev_info to dev_dbg in reset-gpio assertion
> 3. realtek-mdio: add HW reset here too, based on realtek-smi (with
> dev_dbg)
I won't be a problem.
>
> Kind regards,
> Alvin
Powered by blists - more mailing lists