netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	David Miller <davem@davemloft.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Norbert Jurkeit <norbert.jurkeit@web.de>,
	Frank Crawford <frank@crawford.emu.id.au>
Subject: Re: [PATCH net] net: phy: replace preliminary fix for PHY driver sometimes not binding to the device
Date: Tue, 25 Dec 2018 16:17:13 +0100	[thread overview]
Message-ID: <c5271354-e489-6736-a238-7d94d20cd7e5@gmail.com> (raw)
In-Reply-To: <1bafaa75-18a2-87a2-a9cb-01b951c1d1f7@gmail.com>

On 24.12.2018 12:21, Heiner Kallweit wrote:
> phy_device_create() uses request_module() to load the PHY driver module
> based on the PHY ID of the device. There is some timing issue which
> sometimes prevents the PHY driver to bind to the device. In such cases
> the genphy driver is used what can cause problems if genphy isn't
> compatible with the respective PHY.
> It turned out that the first fix can fix the issue in some but not all
> cases. Moving the call to device_initialize() before the call to
> request_module() was reported to fix the issue.
> I can't explain where the root cause of the issue is and why this fix
> works. AFAICS device_initialize() just initializes the device struct
> w/o doing anything that could interfere with e.g. bus_add_driver().
> This patch removes the first preliminary fix attempt.
> 
> Reference:
> https://bugzilla.redhat.com/show_bug.cgi?id=1650984
> 
> Fixes: c85ddecae6e5 ("net: phy: add workaround for issue where PHY driver doesn't bind to the device")
> Tested-by: Norbert Jurkeit <norbert.jurkeit@web.de>
> Tested-by: Frank Crawford <frank@crawford.emu.id.au>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
[..]

I got a report from a user that for him the issue still isn't fixed.
So we need to check alternative approaches. Still I think the root cause
must be in the driver core, therefore set Greg and Rafael on the list.
Could you please wait with applying this patch?

Thanks, Heiner

  reply	other threads:[~2018-12-25 15:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-24 11:21 [PATCH net] net: phy: replace preliminary fix for PHY driver sometimes not binding to the device Heiner Kallweit
2018-12-25 15:17 ` Heiner Kallweit [this message]
2018-12-28 21:02 ` David Miller
2018-12-28 21:56   ` Heiner Kallweit
2018-12-29  2:42 ` Florian Fainelli
2018-12-29  2:48   ` Florian Fainelli
2018-12-29  9:45     ` Heiner Kallweit
2018-12-29 11:46     ` Norbert Jurkeit
2018-12-29 11:54       ` Heiner Kallweit
2018-12-29 13:27         ` Norbert Jurkeit
2018-12-29 13:55           ` Heiner Kallweit
2018-12-29 15:31             ` Norbert Jurkeit
2018-12-29 15:44               ` Heiner Kallweit
2018-12-29 16:59                 ` Norbert Jurkeit
2019-01-06 15:45                   ` Heiner Kallweit
2019-01-03 20:13       ` Heiner Kallweit
2018-12-29  9:33   ` Heiner Kallweit

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=c5271354-e489-6736-a238-7d94d20cd7e5@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=frank@crawford.emu.id.au \
    --cc=gregkh@linuxfoundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=norbert.jurkeit@web.de \
    --cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).