From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] net: phy: realtek: fix RTL8211F interrupt mode
Date: Sun, 12 Nov 2017 19:36:48 +0100 [thread overview]
Message-ID: <1510511808.3550.182.camel@baylibre.com> (raw)
In-Reply-To: <20171112182521.GH30830@lunn.ch>
On Sun, 2017-11-12 at 19:25 +0100, Andrew Lunn wrote:
> On Sun, Nov 12, 2017 at 04:16:04PM +0100, Heiner Kallweit wrote:
> > After commit b94d22d94ad22 "ARM64: dts: meson-gx: add external PHY
> > interrupt on some platforms" ethernet stopped working on my Odroid-C2
> > which has a RTL8211F phy.
>
> Hi Jerome
>
> Please could you test this. I Just want to be sure we don't introduce
> a regression by breaking the boards you tested on.
Sure I'll try it tomorrow.
When I tested this, I was more focused on the SoC side of it (the interrupt
controller itself) and whether the interrupt worked or not. The board (p200) I
tested on used a micrel PHY and worked well ... I did not really expect that a
problem would come from the phy side. This was clearly a mistake.
>
> Thanks
> Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com>
To: Andrew Lunn <andrew@lunn.ch>, Heiner Kallweit <hkallweit1@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
Shengzhou Liu <Shengzhou.Liu@freescale.com>
Subject: Re: [PATCH] net: phy: realtek: fix RTL8211F interrupt mode
Date: Sun, 12 Nov 2017 19:36:48 +0100 [thread overview]
Message-ID: <1510511808.3550.182.camel@baylibre.com> (raw)
In-Reply-To: <20171112182521.GH30830@lunn.ch>
On Sun, 2017-11-12 at 19:25 +0100, Andrew Lunn wrote:
> On Sun, Nov 12, 2017 at 04:16:04PM +0100, Heiner Kallweit wrote:
> > After commit b94d22d94ad22 "ARM64: dts: meson-gx: add external PHY
> > interrupt on some platforms" ethernet stopped working on my Odroid-C2
> > which has a RTL8211F phy.
>
> Hi Jerome
>
> Please could you test this. I Just want to be sure we don't introduce
> a regression by breaking the boards you tested on.
Sure I'll try it tomorrow.
When I tested this, I was more focused on the SoC side of it (the interrupt
controller itself) and whether the interrupt worked or not. The board (p200) I
tested on used a micrel PHY and worked well ... I did not really expect that a
problem would come from the phy side. This was clearly a mistake.
>
> Thanks
> Andrew
next prev parent reply other threads:[~2017-11-12 18:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 15:16 [PATCH] net: phy: realtek: fix RTL8211F interrupt mode Heiner Kallweit
2017-11-12 15:16 ` Heiner Kallweit
2017-11-12 18:25 ` Andrew Lunn
2017-11-12 18:25 ` Andrew Lunn
2017-11-12 18:36 ` Jerome Brunet [this message]
2017-11-12 18:36 ` Jerome Brunet
2017-11-12 20:06 ` Andrew Lunn
2017-11-12 20:06 ` Andrew Lunn
2017-11-12 20:10 ` Jerome Brunet
2017-11-12 20:10 ` Jerome Brunet
2017-11-12 18:29 ` Florian Fainelli
2017-11-12 18:29 ` Florian Fainelli
2017-11-12 18:39 ` Jerome Brunet
2017-11-12 18:39 ` Jerome Brunet
2017-11-13 16:36 ` Jerome Brunet
2017-11-13 16:36 ` Jerome Brunet
2017-11-14 12:34 ` David Miller
2017-11-14 12:34 ` David Miller
2017-12-02 17:14 ` Martin Blumenstingl
2017-12-02 17:14 ` Martin Blumenstingl
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=1510511808.3550.182.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@lists.infradead.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.