From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: tj@kernel.org, kishon@ti.com, Jason Cooper <jason@lakedaemon.net>,
linux-ide@vger.kernel.org
Subject: Re: [patch v2 1/3] drivers: phy: Make NULL a valid phy reference
Date: Mon, 03 Feb 2014 22:15:12 +0100 [thread overview]
Message-ID: <52F006E0.5080903@free-electrons.com> (raw)
In-Reply-To: <1391450446-15580-1-git-send-email-andrew@lunn.ch>
On 03/02/2014 19:00, Andrew Lunn wrote:
> The common clock framework considers NULL a valid clock
> reference. This makes handling optional clocks simple, in that if the
> optional clock is not available, a NULL reference can be used in the
> place of a real clock, simplifying the clock consumer.
>
> Extend this concept to the phy consumer API. A NULL can be passed to
> the release calls, the phy_init() and phy_exit() calls, and
> phy_power_on() and phy_power_off() and a NOP is performed.
>
Hi Andrew,
I have tested these 3 patches on severals Armada 370/XP boards:
- Mirabox
- Armada 370 DB
- OpenBlocks AX3
- Armada XP GP
For all this boards without these series the kernel crash
during boot on v3.14-rc1.
With this series (and "ATA: SATA_MV: Add missing Kconfig
select statememnt" patch), the kernel boot fine on all
these boards.
You can add my
Tested-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
for the whole series.
Thanks,
Gregory
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
> v2
> No change.
> ---
> Documentation/phy.txt | 6 ++++++
> drivers/phy/phy-core.c | 18 ++++++++++++++++++
> 2 files changed, 24 insertions(+)
>
> diff --git a/Documentation/phy.txt b/Documentation/phy.txt
> index 0103e4b15b0e..2e24b993e95f 100644
> --- a/Documentation/phy.txt
> +++ b/Documentation/phy.txt
> @@ -84,6 +84,12 @@ The only difference between the two APIs is that devm_phy_get associates the
> device with the PHY using devres on successful PHY get. On driver detach,
> release function is invoked on the the devres data and devres data is freed.
>
> +It should be noted that NULL is a valid phy reference. All phy
> +consumer calls on the NULL phy become NOPs. That is the release calls,
> +the phy_init() and phy_exit() calls, and phy_power_on() and
> +phy_power_off() calls are all NOP when applied to a NULL phy. The NULL
> +phy is useful in devices for handling optional phy devices.
> +
> 5. Releasing a reference to the PHY
>
> When the controller no longer needs the PHY, it has to release the reference
> diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
> index 645c867c1257..56535253e50c 100644
> --- a/drivers/phy/phy-core.c
> +++ b/drivers/phy/phy-core.c
> @@ -162,6 +162,9 @@ int phy_init(struct phy *phy)
> {
> int ret;
>
> + if (!phy)
> + return 0;
> +
> ret = phy_pm_runtime_get_sync(phy);
> if (ret < 0 && ret != -ENOTSUPP)
> return ret;
> @@ -187,6 +190,9 @@ int phy_exit(struct phy *phy)
> {
> int ret;
>
> + if (!phy)
> + return 0;
> +
> ret = phy_pm_runtime_get_sync(phy);
> if (ret < 0 && ret != -ENOTSUPP)
> return ret;
> @@ -212,6 +218,9 @@ int phy_power_on(struct phy *phy)
> {
> int ret;
>
> + if (!phy)
> + return 0;
> +
> ret = phy_pm_runtime_get_sync(phy);
> if (ret < 0 && ret != -ENOTSUPP)
> return ret;
> @@ -240,6 +249,9 @@ int phy_power_off(struct phy *phy)
> {
> int ret;
>
> + if (!phy)
> + return 0;
> +
> mutex_lock(&phy->mutex);
> if (phy->power_count == 1 && phy->ops->power_off) {
> ret = phy->ops->power_off(phy);
> @@ -308,6 +320,9 @@ err0:
> */
> void phy_put(struct phy *phy)
> {
> + if (!phy)
> + return;
> +
> if (IS_ERR(phy))
> return;
>
> @@ -328,6 +343,9 @@ void devm_phy_put(struct device *dev, struct phy *phy)
> {
> int r;
>
> + if (!phy)
> + return;
> +
> r = devres_destroy(dev, devm_phy_release, devm_phy_match, phy);
> dev_WARN_ONCE(dev, r, "couldn't find PHY resource\n");
> }
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2014-02-03 21:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0140131114857.GC26148@htj.dyndns.org>
2014-02-01 14:15 ` [PATCH 1/3] drivers: phy: Make NULL a valid phy reference Andrew Lunn
2014-02-01 14:15 ` [PATCH 2/3] drivers: phy: Add support for optional phys Andrew Lunn
2014-02-03 5:51 ` Kishon Vijay Abraham I
2014-02-03 9:36 ` Andrew Lunn
2014-02-03 10:19 ` Kishon Vijay Abraham I
2014-02-03 18:00 ` [patch v2 1/3] drivers: phy: Make NULL a valid phy reference Andrew Lunn
2014-02-03 18:00 ` [patch v2 2/3] drivers: phy: Add support for optional phys Andrew Lunn
2014-02-03 18:00 ` [patch v2 3/3] ata: sata_mv: Fix probe failures with " Andrew Lunn
2014-02-03 18:02 ` Tejun Heo
2014-02-03 19:04 ` Sergei Shtylyov
2014-02-03 18:17 ` [patch v3 " Andrew Lunn
2014-02-03 19:21 ` Sergei Shtylyov
2014-02-03 19:06 ` [patch v2 1/3] drivers: phy: Make NULL a valid phy reference Sergei Shtylyov
2014-02-03 18:13 ` Andrew Lunn
2014-02-03 19:17 ` Sergei Shtylyov
2014-02-03 21:15 ` Gregory CLEMENT [this message]
2014-02-01 14:15 ` [PATCH 3/3] ata: sata_mv: Fix probe failures with optional phys Andrew Lunn
2014-02-01 14:44 ` Ezequiel Garcia
2014-02-01 14:56 ` Andrew Lunn
2014-02-01 15:36 ` Ezequiel Garcia
2014-02-03 16:03 ` Tejun Heo
2014-02-03 16:20 ` Andrew Lunn
2014-02-03 16:21 ` Tejun Heo
2014-02-03 16:21 ` Gregory CLEMENT
2014-02-03 17:17 ` Gregory CLEMENT
2014-02-03 17:23 ` Andrew Lunn
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=52F006E0.5080903@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=jason@lakedaemon.net \
--cc=kishon@ti.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.