[<prev] [next>] [day] [month] [year] [list]
Message-ID: <4ECA2E9C.1000207@atmel.com>
Date: Mon, 21 Nov 2011 11:57:32 +0100
From: Nicolas Ferre <nicolas.ferre@...el.com>
To: Shawn Guo <shawn.guo@...escale.com>,
Grant Likely <grant.likely@...retlab.ca>,
devicetree-discuss@...ts.ozlabs.org,
devicetree-discuss@...ts.ozlabs.org
CC: "'linux-arm-kernel@...ts.infradead.org'"
<linux-arm-kernel@...ts.infradead.org>, netdev@...r.kernel.org,
Rob Herring <robherring2@...il.com>
Subject: Re: [PATCH v2 1/3] dt/net: add helper function of_get_phy_mode
Hi all,
> It adds the helper function of_get_phy_mode getting phy interface
> from device tree.
>
> Signed-off-by: Shawn Guo <shawn.guo <at> linaro.org>
> Cc: Grant Likely <grant.likely <at> secretlab.ca>
> ---
> drivers/of/of_net.c | 43 +++++++++++++++++++++++++++++++++++++++++++
> include/linux/of_net.h | 1 +
[..]
> +const int of_get_phy_mode(struct device_node *np)
Nice helper function, indeed.
> +{
> + const char *pm;
> + int err, i;
> +
> + err = of_property_read_string(np, "phy-mode", &pm);
Just a quick question about the use of the "phy-mode" string:
- I know that it is widely used in drivers
- but, I discovered that in the ePAPR the string mentioned is "phy-connection-type" (6.5.2.2)
- and it is true also that in the very same document, we find the "phy-mode" in the Appendix B1 example...
Why this naming is not consistent (even in ePAPR)?
Best regards,
--
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists