From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH net-next v3 2/2] ixgbe: use mii_bus to handle MII related ioctls Date: Mon, 3 Dec 2018 20:01:22 +0100 Message-ID: <20181203190122.GQ25748@lunn.ch> References: <20181203163227.5107-1-stephend@silicom-usa.com> <20181203185454.6357-1-stephend@silicom-usa.com> <20181203185454.6357-3-stephend@silicom-usa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jeff Kirsher , "David S. Miller" , "intel-wired-lan@lists.osuosl.org" , "netdev@vger.kernel.org" , Florian Fainelli To: Steve Douthit Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:59335 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725991AbeLCTBc (ORCPT ); Mon, 3 Dec 2018 14:01:32 -0500 Content-Disposition: inline In-Reply-To: <20181203185454.6357-3-stephend@silicom-usa.com> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Dec 03, 2018 at 06:55:26PM +0000, Steve Douthit wrote: > Use the mii_bus callbacks to address the entire clause 22/45 address > space. Enables userspace to poke switch registers instead of a single > PHY address. > > The ixgbe firmware may be polling PHYs in a way that is not protected by > the mii_bus lock. This isn't new behavior, but as Andrew Lunn pointed > out there are more addresses available for conflicts. > > Signed-off-by: Stephen Douthit Reviewed-by: Andrew Lunn Andrew