On 14/01/2021 16:56, Jon Hunter wrote:
>
> On 14/01/2021 16:47, Saravana Kannan wrote:
>
> ...
>
>>> Yes this is the warning shown here [0] and this is coming from
>>> the 'Generic PHY stmmac-0:00' device.
>>
>> Can you print the supplier and consumer device when this warning is
>> happening and let me know? That'd help too. I'm guessing the phy is
>> the consumer.
>
>
> Sorry I should have included that. I added a print to dump this on
> another build but failed to include here.
>
> WARNING KERN Generic PHY stmmac-0:00: supplier 2200000.gpio (status 1)
>
> The status is the link->status and looks like the supplier is the
> gpio controller. I have verified that the gpio controller is probed
> before this successfully.
>
>> So the warning itself isn't a problem -- it's not breaking anything or
>> leaking memory or anything like that. But the device link is jumping
>> states in an incorrect manner. With enough context of this code (why
>> the device_bind_driver() is being called directly instead of going
>> through the normal probe path), it should be easy to fix (I'll just
>> need to fix up the device link state).
>
> Correct, the board seems to boot fine, we just get this warning.
Have you had chance to look at this further?
The following does appear to avoid the warning, but I am not sure if
this is the correct thing to do ...
index 9179825ff646..095aba84f7c2 100644
--- a/drivers/base/dd.c
+++ b/drivers/base/dd.c
@@ -456,6 +456,10 @@ int device_bind_driver(struct device *dev)
{
int ret;
+ ret = device_links_check_suppliers(dev);
+ if (ret)
+ return ret;
+
ret = driver_sysfs_add(dev);
if (!ret)
driver_bound(dev);
Cheers
Jon
--
nvpublic
