lkml.org 
[lkml]   [2014]   [Feb]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 6/8] phy-core: Don't propagate -ENOSUPP from phy_pm_runtime_get_sync to caller
    Date
    From: Hans de Goede <hdegoede@redhat.com>

    The phy-core allows phy_init and phy_power_on to be called multiple times,
    but before this patch -ENOSUPP from phy_pm_runtime_get_sync would be
    propagated to the caller for the 2nd and later calls.

    Signed-off-by: Hans de Goede <hdegoede@redhat.com>
    Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
    ---
    drivers/phy/phy-core.c | 4 ++++
    1 file changed, 4 insertions(+)

    diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
    index b355553..6c73837 100644
    --- a/drivers/phy/phy-core.c
    +++ b/drivers/phy/phy-core.c
    @@ -176,6 +176,8 @@ int phy_init(struct phy *phy)
    dev_err(&phy->dev, "phy init failed --> %d\n", ret);
    goto out;
    }
    + } else {
    + ret = 0; /* Override possible ret == -ENOTSUPP */
    }
    ++phy->init_count;

    @@ -232,6 +234,8 @@ int phy_power_on(struct phy *phy)
    dev_err(&phy->dev, "phy poweron failed --> %d\n", ret);
    goto out;
    }
    + } else {
    + ret = 0; /* Override possible ret == -ENOTSUPP */
    }
    ++phy->power_count;
    mutex_unlock(&phy->mutex);
    --
    1.7.10.4


    \
     
     \ /
      Last update: 2014-02-17 17:41    [W:3.075 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site