[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BL0PR11MB29131080A183B94D1E4F1C39E7EA9@BL0PR11MB2913.namprd11.prod.outlook.com>
Date: Tue, 20 Dec 2022 19:43:28 +0000
From: <Woojung.Huh@...rochip.com>
To: <andrew@...n.ch>, <enguerrand.de-ribaucourt@...oirfairelinux.com>
CC: <hkallweit1@...il.com>, <netdev@...r.kernel.org>,
<pabeni@...hat.com>, <davem@...emloft.net>,
<UNGLinuxDriver@...rochip.com>, <linux@...linux.org.uk>
Subject: RE: [PATCH v3 1/3] net: phy: add EXPORT_SYMBOL to
phy_disable_interrupts()
Hi Andrew,
Let me check with our team.
Best regards,
Woojung
> -----Original Message-----
> From: Andrew Lunn <andrew@...n.ch>
> Sent: Tuesday, December 20, 2022 11:55 AM
> To: Enguerrand de Ribaucourt <enguerrand.de-
> ribaucourt@...oirfairelinux.com>
> Cc: Heiner Kallweit <hkallweit1@...il.com>; netdev
> <netdev@...r.kernel.org>; Paolo Abeni <pabeni@...hat.com>; Woojung
> Huh - C21699 <Woojung.Huh@...rochip.com>; davem
> <davem@...emloft.net>; UNGLinuxDriver
> <UNGLinuxDriver@...rochip.com>; Russell King - ARM Linux
> <linux@...linux.org.uk>
> Subject: Re: [PATCH v3 1/3] net: phy: add EXPORT_SYMBOL to
> phy_disable_interrupts()
>
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> On Tue, Dec 20, 2022 at 10:48:25AM -0500, Enguerrand de Ribaucourt wrote:
> > > From: "Heiner Kallweit" <hkallweit1@...il.com>
> > > To: "Enguerrand de Ribaucourt" <enguerrand.de-
> ribaucourt@...oirfairelinux.com>
> > > Cc: "netdev" <netdev@...r.kernel.org>, "Paolo Abeni"
> <pabeni@...hat.com>, "woojung huh" <woojung.huh@...rochip.com>,
> > > "davem" <davem@...emloft.net>, "UNGLinuxDriver"
> <UNGLinuxDriver@...rochip.com>, "Andrew Lunn" <andrew@...n.ch>,
> > > "Russell King - ARM Linux" <linux@...linux.org.uk>
> > > Sent: Tuesday, December 20, 2022 4:19:40 PM
> > > Subject: Re: [PATCH v3 1/3] net: phy: add EXPORT_SYMBOL to
> phy_disable_interrupts()
> > My proposed approach would be to copy the original workaround actions
> > within link_change_notify():
> > 1. disable interrupts
> > 2. reset speed
> > 3. enable interrupts
> >
> > However, I don't have access to the LAN8835 to test if this would work. I
> also
> > don't have knowledge about which other Microchip PHYs could be
> impacted. Maybe
> > there is an active Microchip developer we could communicate with to find
> out?
>
> Woojung Huh added this code, and he sometimes contributes here.
>
> Woojung, do you still have access to the hardware?
>
> Andrew
Powered by blists - more mailing lists