From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of_mdio: Fix broken PHY IRQ in case of probe deferral
Date: Sun, 9 Jul 2017 19:28:15 +0200 [thread overview]
Message-ID: <20170709172815.GA28183@lunn.ch> (raw)
In-Reply-To: <38cc7c65-e4ca-cb8a-f43b-ca53e87724cf@gmail.com>
> It sure does fix a real issue, but I am really concerned about the
> inability to test this patch in a configuration where we have multiple
> PHY(s) or MDIO device(s) hanging off the same MDIO bus and one of those
> requesting an EPROBE_DEFER.
>
> I currently don't have a setup where I could exercise this, Andrew, do you?
Hi Florian
What i do have, is a switch with some built in copper Marvell PHYs and
external SFF modules which use fixed link. I can probably hack the
fixed-link driver to return EPROBE_DEFER a few times.
Andrew
next prev parent reply other threads:[~2017-07-09 17:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 12:59 [PATCH] of_mdio: Fix broken PHY IRQ in case of probe deferral Geert Uytterhoeven
2017-05-18 12:59 ` Geert Uytterhoeven
2017-05-18 15:21 ` David Miller
2017-05-18 15:21 ` David Miller
2017-05-18 16:09 ` Andrew Lunn
2017-05-18 16:13 ` Geert Uytterhoeven
2017-05-18 16:33 ` Andrew Lunn
2017-05-18 16:33 ` Andrew Lunn
2017-05-18 17:38 ` Geert Uytterhoeven
2017-05-18 18:25 ` Florian Fainelli
2017-05-18 18:48 ` Geert Uytterhoeven
2017-05-18 19:34 ` Andrew Lunn
2017-05-18 20:36 ` Geert Uytterhoeven
2017-05-18 22:21 ` Florian Fainelli
2017-05-23 9:36 ` Geert Uytterhoeven
2017-05-23 9:36 ` Geert Uytterhoeven
2017-06-06 9:43 ` Geert Uytterhoeven
2017-07-02 20:37 ` Geert Uytterhoeven
2017-07-02 20:37 ` Geert Uytterhoeven
2017-07-09 16:49 ` Florian Fainelli
2017-07-09 17:28 ` Andrew Lunn [this message]
2017-07-09 19:38 ` Geert Uytterhoeven
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=20170709172815.GA28183@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=thomas.petazzoni@free-electrons.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.