From: Andrew Lunn <andrew@lunn.ch>
To: Harini Katakam <harinik@xilinx.com>
Cc: Harini Katakam <harini.katakam@xilinx.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
David Miller <davem@davemloft.net>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [RFC PATCH 1/2] dt-bindings: net: macb: Add new property for PS SGMII only
Date: Mon, 5 Aug 2019 19:16:39 +0200 [thread overview]
Message-ID: <20190805171639.GV24275@lunn.ch> (raw)
In-Reply-To: <CAFcVECLVHY5X=wctxVqRqDTDyG7Zavkt5ui4RtFBLP8g8MW1SA@mail.gmail.com>
> Even with the use of this interrupt, the link status actions (link print and
> netif ops) will still be required. And also the need for macb_open to
> proceed without phydev. Could you please let me know if that is acceptable
> to patch or if there's a cleaner way to
> report this link status?
It sounds like you need to convert to phylink, so you get full sfp
support. phylib does not handle hotplug of PHYs.
Please look at the comments Russell gave the last time this was
attempted.
Andrew
next prev parent reply other threads:[~2019-08-05 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 9:40 [RFC PATCH 0/2] Macb SGMII status poll thread Harini Katakam
2019-07-31 9:40 ` [RFC PATCH 1/2] dt-bindings: net: macb: Add new property for PS SGMII only Harini Katakam
2019-08-04 14:56 ` Andrew Lunn
2019-08-05 6:15 ` Harini Katakam
2019-08-05 13:20 ` Andrew Lunn
2019-08-05 14:36 ` Harini Katakam
2019-08-05 16:10 ` Harini Katakam
2019-08-05 17:16 ` Andrew Lunn [this message]
2019-08-06 5:47 ` Harini Katakam
2019-07-31 9:40 ` [RFC PATCH 2/2] net: macb: Add SGMII poll thread Harini Katakam
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=20190805171639.GV24275@lunn.ch \
--to=andrew@lunn.ch \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=harini.katakam@xilinx.com \
--cc=harinik@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.