From: Florian Fainelli <f.fainelli@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] irqchip/renesas-irqc: Postpone driver initialization
Date: Wed, 9 Nov 2016 11:17:05 -0800 [thread overview]
Message-ID: <3dface9b-7602-b1f2-0dd6-37b444ac42e3@gmail.com> (raw)
In-Reply-To: <CAMuHMdWkXsAuRpbTWGw9Wp4m2M38zRAd8OpPpA-sCDb7Xb7skw@mail.gmail.com>
On 11/08/2016 11:50 AM, Geert Uytterhoeven wrote:
> Hi Florian,
>
> On Tue, Nov 8, 2016 at 8:42 PM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> On 11/08/2016 11:35 AM, Geert Uytterhoeven wrote:
>>> Currently the renesas-irqc driver uses postcore_initcall().
>>>
>>> However, the new CPG/MSSR driver uses subsys_initcall(). Hence the
>>> IRQC's probe will be deferred, which causes the Micrel Ethernet PHY to
>>> not find its interrupt on R-Car Gen2 and RZ/G, as the of_mdio subsystem
>>> does not support deferred probe yet.
>>
>> Is not that the more correct fix to implement though?
>
> Sure it is. But nothing has happened since this was reported ca. 1 year ago.
> Cfr. "of_mdiobus_register_phy() and deferred probe"
> https://lkml.org/lkml/2015/10/22/377
>
> My MDIO foo is not that strong...
Let me try to cook something here which may require
of_mdiobus_register_phy(), are you okay testing patches?
--
Florian
next prev parent reply other threads:[~2016-11-09 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 19:35 [PATCH v2] irqchip/renesas-irqc: Postpone driver initialization Geert Uytterhoeven
2016-11-08 19:42 ` Florian Fainelli
2016-11-08 19:50 ` Geert Uytterhoeven
2016-11-09 19:17 ` Florian Fainelli [this message]
2016-11-09 19:43 ` Geert Uytterhoeven
2016-11-09 9:03 ` Marc Zyngier
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=3dface9b-7602-b1f2-0dd6-37b444ac42e3@gmail.com \
--to=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marc.zyngier@arm.com \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.