From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: Q: force netif ON even when there is no real link ? Date: Fri, 20 Apr 2018 14:05:16 +0200 Message-ID: <20180420120516.GC20256@lunn.ch> References: <20180420115556.GB20256@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org To: Ran Shalit Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:35307 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754591AbeDTMFR (ORCPT ); Fri, 20 Apr 2018 08:05:17 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Fri, Apr 20, 2018 at 03:01:09PM +0300, Ran Shalit wrote: > On Fri, Apr 20, 2018 at 2:55 PM, Andrew Lunn wrote: > > On Fri, Apr 20, 2018 at 11:44:14AM +0300, Ran Shalit wrote: > >> Hello, > >> > >> We configure external switch in u-boot. > >> The configuration is through mdio (cpu is mac and switch is phy). > >> > >> But in Linux we rather not implement any communication in mdio to > >> switch, but it means that we then don't have the information of link > >> state. > >> > >> Is it possible to force in Linux (by default in startup) Ethernet > >> connectivity (netif_carrier_on, netif_wake_queue) even if there is no > >> information of real link state ? > > > > Hi Ran > > > > Use a fixed-phy. > > > > Hi Andrew, > > I'll check about fixed phy, > but in general, is it a problem to have always netif_carrier_on, even > when there is no link ? The link between the CPU and the switch should be up all the time. That is the point of fixed-link. Andrew