From: Andrew Lunn <andrew@lunn.ch>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "claudiu.manoil@nxp.com" <claudiu.manoil@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] gianfar: Add gfar_change_carrier()
Date: Thu, 6 Dec 2018 17:21:31 +0100 [thread overview]
Message-ID: <20181206162131.GG18674@lunn.ch> (raw)
In-Reply-To: <a14732322dfdaa36c4739fc42ef94c3477fe0d72.camel@infinera.com>
> > Hi Joakim
> >
> > Please could you explain the use case for this.
>
> I have an eth I/F connected to an internal (on board) switch which has an external port to a mgmt network.
> Whenever the external link is broken I want inform linux IP stack that the link is down on the internal eth
> I/F as well. The two interfaces are isolated from the rest of the switch ports using VLANs.
Hi Jockim
What type of switch is it?
What i would expect is you use a switch driver, and that driver would
allow access to the switches PHYs. When the external port goes down,
the Linux interface for that port would go down. There is no need to
change the carrier on the master interface.
Andrew
next prev parent reply other threads:[~2018-12-06 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 15:31 [PATCH] gianfar: Add gfar_change_carrier() Joakim Tjernlund
2018-12-06 15:47 ` Andrew Lunn
2018-12-06 16:02 ` Joakim Tjernlund
2018-12-06 16:21 ` Andrew Lunn [this message]
2018-12-06 16:31 ` Joakim Tjernlund
2018-12-06 16:54 ` Andrew Lunn
2018-12-06 18:46 ` Joakim Tjernlund
2018-12-06 19:43 ` Andrew Lunn
2018-12-07 14:07 ` Joakim Tjernlund
2018-12-07 14:15 ` Andrew Lunn
2018-12-07 17:01 ` Joakim Tjernlund
2018-12-07 17:26 ` Andrew Lunn
2018-12-07 20:40 ` Florian Fainelli
2018-12-10 15:37 ` Joakim Tjernlund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181206162131.GG18674@lunn.ch \
--to=andrew@lunn.ch \
--cc=Joakim.Tjernlund@infinera.com \
--cc=claudiu.manoil@nxp.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).