From: Daniel Mack <zonque@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
mugunthanvnm <mugunthanvnm@ti.com>,
Matus Ujhelyi <ujhelyi.m@gmail.com>
Subject: Re: [PATCH 2/3] net: of_mdio: add of_mdiobus_link_phydev()
Date: Sat, 24 May 2014 09:25:57 +0200 [thread overview]
Message-ID: <53804985.7030204@gmail.com> (raw)
In-Reply-To: <CAGVrzcbPd8c9Q3njGX=YutZyrP+y5BSUS-bZeJje-_AaSy_tqA@mail.gmail.com>
On 05/23/2014 09:35 PM, Florian Fainelli wrote:
> 2014-05-10 9:37 GMT-07:00 Daniel Mack <zonque@gmail.com>:
>> +/**
>> + * of_mdiobus_link_phydev - Find a device node for a phy
>> + * @mdio: pointer to mii_bus structure
>> + * @phydev: phydev for which the of_node pointer should be set
>> + *
>> + * Walk the list of subnodes of a mdio bus and look for a node that matches the
>> + * phy's address with its 'reg' property. If found, set the of_node pointer for
>> + * the phy. This allows auto-probed pyh devices to be supplied with information
>> + * passed in via DT.
>> + */
>> +void of_mdiobus_link_phydev(struct mii_bus *mdio,
>> + struct phy_device *phydev)
>> +{
>> + struct device *dev = &phydev->dev;
>> + struct device_node *child;
>> +
>> + if (dev->of_node)
>> + return;
>
> This should be:
>
> if (dev->of_node || !mdio->dev_of_node)
> return;
>
> a system with for instance non-DT probed MDIO busses such as the
> special fixed MDIO bus will not have such an of_node pointer and we
> will have a null pointer during the first iteration of the for_each_*
> loop.
>
> arguably of_get_next_available_child() could be updated to handle a
> NULL parent device_node, but I think it clearer to add this check
> here.
Good catch! I'll change that, add your Reviewed-by and resend!
Thanks,
Daniel
next prev parent reply other threads:[~2014-05-24 7:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 16:37 [PATCH 0/3] mdio: Parse DT nodes for auto-probed PHYs Daniel Mack
2014-05-10 16:37 ` [PATCH 1/3] net: of_mdio: factor out code to parse a phy's 'reg' property Daniel Mack
2014-05-10 20:29 ` Sergei Shtylyov
2014-05-13 17:07 ` David Miller
2014-05-13 17:21 ` Daniel Mack
2014-05-13 17:25 ` David Miller
2014-05-13 17:29 ` Daniel Mack
2014-05-10 16:37 ` [PATCH 2/3] net: of_mdio: add of_mdiobus_link_phydev() Daniel Mack
2014-05-23 19:35 ` Florian Fainelli
2014-05-24 7:25 ` Daniel Mack [this message]
2014-05-10 16:37 ` [PATCH 3/3] net: of_mdio: don't store the length of a property if we don't need to Daniel Mack
2014-05-13 4:33 ` [PATCH 0/3] mdio: Parse DT nodes for auto-probed PHYs Florian Fainelli
2014-05-22 18:18 ` Daniel Mack
2014-05-23 19:24 ` Florian Fainelli
2014-05-23 19:26 ` Florian Fainelli
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=53804985.7030204@gmail.com \
--to=zonque@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=ujhelyi.m@gmail.com \
/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).