[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1b4d53d9-b797-4a4b-bce5-227efedac451@lunn.ch>
Date: Mon, 2 Sep 2024 22:39:37 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Rosen Penev <rosenp@...il.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, linux-kernel@...r.kernel.org,
jacob.e.keller@...el.com, horms@...nel.org, sd@...asysnail.net,
chunkeey@...il.com
Subject: Re: [PATCH 2/6] net: ibm: emac: manage emac_irq with devm
> > Is this an internal interrupt, or a GPIO? It could be it is done in
> > open because there is a danger the GPIO controller has not probed
> > yet. So here you might get an EPROBE_DEFFER, where as the much older
> > kernel this was written for might not of done, if just gave an error
> > had gave up. So dev_err_probe() might be better.
> Good call on that. In my experience, I get these EPROBE_DEFER errors
> on OpenWrt's ath79 target (QCA MIPS) but not on PowerPC when trying to
> use GPIOs. Nevertheless it seems to be good practice to use
> dev_err_probe anyway. Will fix in v2.
You might want to look at
https://elixir.bootlin.com/linux/v6.10.7/source/drivers/net/ethernet/ibm/emac/core.c#L2418
and then replace it by correctly handling EPROBE_DEFER.
As you said, an old driver, needing some cleanup.
Andrew
Powered by blists - more mailing lists