[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CO2PR07MB2469C003D5583A2AD1FAA833C1EA0@CO2PR07MB2469.namprd07.prod.outlook.com>
Date: Tue, 18 Jun 2019 18:22:18 +0000
From: Parshuram Raju Thombare <pthombar@...ence.com>
To: Andrew Lunn <andrew@...n.ch>
CC: "nicolas.ferre@...rochip.com" <nicolas.ferre@...rochip.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"hkallweit1@...il.com" <hkallweit1@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rafal Ciepiela <rafalc@...ence.com>,
Anil Joy Varughese <aniljoy@...ence.com>,
Piotr Sroka <piotrs@...ence.com>
Subject: RE: [PATCH 1/6] net: macb: add phylink support
>> @@ -4217,8 +4257,8 @@ static int macb_probe(struct platform_device *pdev)
>>
>> tasklet_init(&bp->hresp_err_tasklet, macb_hresp_error_task,
>> (unsigned long)bp);
>> -
>> - phy_attached_info(phydev);
>> + if (dev->phydev)
>> + phy_attached_info(dev->phydev);
>
>When can this happen? I don't see anything assigning to dev->phydev.
This is for non sfp (MDIO) based PHY. It is set in phy_attach_direct (phylink_connect_phy -> __ phylink_connect_phy -> phy_attach_direct)
>
> Andrew
Regards,
Parshuram Thombare
Powered by blists - more mailing lists