From: Mason <slash.tmp@free.fr>
To: Zefir Kurtisi <zefir.kurtisi@neratec.com>,
netdev <netdev@vger.kernel.org>
Cc: Mans Rullgard <mans@mansr.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>
Subject: Re: Setting link down or up in software
Date: Fri, 13 Jan 2017 18:35:57 +0100 [thread overview]
Message-ID: <660b7b17-0136-bf69-fd12-1c125069829b@free.fr> (raw)
In-Reply-To: <bfe5bd8b-d4eb-8c8e-45d8-6ea1c133b4a7@neratec.com>
On 13/01/2017 17:28, Zefir Kurtisi wrote:
> As for your specific problem: since I fought myself with the PHY/ETH subsystems
> over the past months, I might remember something relevant to your issue. Could you
> give some more info on your setup (PHY driver, opmode (SGMII, RGMII, etc.), ETH).
Hello Zefir,
My boards are using these drivers:
http://lxr.free-electrons.com/source/drivers/net/ethernet/aurora/nb8800.c
http://lxr.free-electrons.com/source/drivers/net/phy/at803x.c
The relevant device tree nodes are:
eth0: ethernet@26000 {
compatible = "sigma,smp8734-ethernet";
reg = <0x26000 0x800>;
interrupts = <38 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&clkgen SYS_CLK>;
};
ð0 {
phy-connection-type = "rgmii";
phy-handle = <ð0_phy>;
#address-cells = <1>;
#size-cells = <0>;
/* Atheros AR8035 */
eth0_phy: ethernet-phy@4 {
compatible = "ethernet-phy-id004d.d072",
"ethernet-phy-ieee802.3-c22";
interrupts = <37 IRQ_TYPE_EDGE_RISING>;
reg = <4>;
};
};
If I comment the PHY "interrupts" property, then the PHY framework
falls back to polling.
Am I forgetting important information?
Regards.
next prev parent reply other threads:[~2017-01-13 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 13:05 Setting link down or up in software Mason
2017-01-12 15:16 ` Mason
2017-01-12 15:28 ` Andrew Lunn
2017-01-12 16:22 ` Mason
2017-01-12 16:27 ` Andrew Lunn
2017-01-12 18:45 ` Dan Williams
2017-01-13 9:20 ` Zefir Kurtisi
2017-01-13 15:17 ` Mason
2017-01-13 16:28 ` Zefir Kurtisi
2017-01-13 17:35 ` Mason [this message]
2017-01-18 10:29 ` Zefir Kurtisi
2017-01-19 15:40 ` Mason
2017-01-19 17:56 ` Måns Rullgård
2017-01-19 17:59 ` Florian Fainelli
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=660b7b17-0136-bf69-fd12-1c125069829b@free.fr \
--to=slash.tmp@free.fr \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=thibaud_cornic@sigmadesigns.com \
--cc=zefir.kurtisi@neratec.com \
/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.