From: Florian Fainelli <f.fainelli@gmail.com>
To: Alexander Graf <agraf@suse.de>, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, michal.simek@xilinx.com,
Dan Murphy <dmurphy@ti.com>,
andrew@lunn.ch
Subject: Re: [PATCH v2 2/2] phy dp83867: Make rgmii parameters optional
Date: Mon, 16 May 2016 12:04:04 -0700 [thread overview]
Message-ID: <573A19A4.6060306@gmail.com> (raw)
In-Reply-To: <1463424763-58807-2-git-send-email-agraf@suse.de>
On 05/16/2016 11:52 AM, Alexander Graf wrote:
> If you compile without OF_MDIO support in an RGMII configuration, we fail
> to configure the dp83867 phy today by writing garbage into its configuration
> registers.
>
> On the other hand if you do compile with OF_MDIO and the phy gets loaded via
> device tree, you have to have the properties set in the device tree, otherwise
> we fail to load the driver and don't even attach the generic phy driver to
> the interface anymore.
>
> To make things slightly more consistent, make the rgmii configuration properties
> optional and allow a user to omit them in their device tree.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> drivers/net/phy/dp83867.c | 31 ++++++++++++++++++++++++++++---
> 1 file changed, 28 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/phy/dp83867.c b/drivers/net/phy/dp83867.c
> index 94cc278..1b01680 100644
> --- a/drivers/net/phy/dp83867.c
> +++ b/drivers/net/phy/dp83867.c
> @@ -65,6 +65,7 @@ struct dp83867_private {
> int rx_id_delay;
> int tx_id_delay;
> int fifo_depth;
> + int values_are_sane;
This could be a boolean type.
> };
>
> static int dp83867_ack_interrupt(struct phy_device *phydev)
> @@ -113,15 +114,30 @@ static int dp83867_of_init(struct phy_device *phydev)
> ret = of_property_read_u32(of_node, "ti,rx-internal-delay",
> &dp83867->rx_id_delay);
> if (ret)
> - return ret;
> + goto invalid_dt;
>
> ret = of_property_read_u32(of_node, "ti,tx-internal-delay",
> &dp83867->tx_id_delay);
> if (ret)
> - return ret;
> + goto invalid_dt;
>
> - return of_property_read_u32(of_node, "ti,fifo-depth",
> + ret = of_property_read_u32(of_node, "ti,fifo-depth",
> &dp83867->fifo_depth);
> + if (ret)
> + goto invalid_dt;
> +
> + dp83867->values_are_sane = 1;
> +
> + return 0;
> +
> +invalid_dt:
> + phydev_err(phydev, "missing properties in device tree");
phydev_warn() maybe?
Other than that, this looks okay to me.
--
Florian
next prev parent reply other threads:[~2016-05-16 19:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 18:52 [PATCH v2 1/2] phy dp83867: Fix compilation with CONFIG_OF_MDIO=m Alexander Graf
2016-05-16 18:52 ` [PATCH v2 2/2] phy dp83867: Make rgmii parameters optional Alexander Graf
2016-05-16 19:04 ` Florian Fainelli [this message]
2016-05-16 20:15 ` Andrew Lunn
2016-05-16 20:27 ` Dan Murphy
2016-05-17 18:22 ` David Miller
2016-05-17 18:34 ` Dan Murphy
2016-05-17 18:48 ` David Miller
2016-05-17 20:37 ` Alexander Graf
2016-05-17 20:40 ` Dan Murphy
2016-05-17 20:45 ` Alexander Graf
2016-05-17 18:22 ` [PATCH v2 1/2] phy dp83867: Fix compilation with CONFIG_OF_MDIO=m David Miller
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=573A19A4.6060306@gmail.com \
--to=f.fainelli@gmail.com \
--cc=agraf@suse.de \
--cc=andrew@lunn.ch \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
/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).