linux-stable.git/drivers/phy/phy-core.c, branch linux-3.17.y

phy: core: Let node ptr of PHY point to PHY and not of PHY provider

2014-07-22T07:16:11+00:00

In case of multi-phy PHY providers, each PHY should be modeled as a sub
node of the PHY provider. Then each PHY will have a different node pointer
(node pointer of sub node) than that of PHY provider. Added this provision
in the PHY core.
Also fixed all drivers to use the updated API.

Signed-off-by: Kishon Vijay Abraham I 
Acked-by: Lee Jones

phy: core: Fix of_phy_provider_lookup to return PHY provider for sub node

2014-07-22T07:16:11+00:00

Fixed of_phy_provider_lookup to return 'phy_provider' if _of_phy_get
passes the node pointer of the sub-node of phy provider node. This is
needed when phy provider implements multiple PHYs and each PHY is
modelled as the sub-node of PHY provider device node.

Signed-off-by: Kishon Vijay Abraham I 
Acked-by: Lee Jones

phy: core: Support regulator supply for PHY power

2014-07-22T07:16:10+00:00

Some PHYs can be powered by an external power regulator.
e.g. USB_HS PHY on DRA7 SoC. Make the PHY core support a
power regulator.

Signed-off-by: Roger Quadros 
Signed-off-by: Kishon Vijay Abraham I

phy: core: Fix error path in phy_create()

2014-07-12T01:23:49+00:00

Prevent resources from being freed twice in case device_add() call
fails within phy_create(). Also use ida_simple_remove() instead of
ida_remove() as we had used ida_simple_get() to allocate the ida.

Cc: 3.13+  # 3.13+
Signed-off-by: Roger Quadros 
Signed-off-by: Kishon Vijay Abraham I 
Signed-off-by: Greg Kroah-Hartman

phy: fix kernel oops in phy_lookup()

2014-04-24T19:53:38+00:00

The kernel oopses in phy_lookup() due to 'phy->init_data' being NULL if we
register PHYs from a device tree probing driver and then call phy_get() on a
device that has no representation in the device tree (e.g. a PCI device).
Checking the pointer before dereferening it and skipping an interation if
it's NULL prevents this kernel oops.

Signed-off-by: Sergei Shtylyov 
Signed-off-by: Kishon Vijay Abraham I 
Signed-off-by: Greg Kroah-Hartman

phy: core: Add devm_of_phy_get to phy-core

2014-03-08T07:09:43+00:00

Adding devm_of_phy_get will allow to get phys by supplying a
pointer to the struct device_node instead of struct device.

Signed-off-by: Kamil Debski 
Reviewed-by: Tomasz Figa 
Signed-off-by: Kishon Vijay Abraham I

phy: core: Add an exported of_phy_get function

2014-03-08T07:09:42+00:00

Previously the of_phy_get function took a struct device * and
was declared static. It was impossible to call it from
another driver and thus it was impossible to get phy defined
for a given node. The old function was renamed to _of_phy_get
and was left for internal use. of_phy_get function was added
and it was exported. The function enables to get a phy for
a given device tree node.

Signed-off-by: Kamil Debski 
Reviewed-by: Tomasz Figa 
Signed-off-by: Kishon Vijay Abraham I

phy-core: Don't propagate -ENOSUPP from phy_pm_runtime_get_sync to caller

2014-02-18T20:13:16+00:00

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 
Signed-off-by: Kishon Vijay Abraham I 
Signed-off-by: Greg Kroah-Hartman

phy-core: phy_get: Leave error logging to the caller

2014-02-18T20:13:15+00:00

In various cases errors may be expected, ie probe-deferral or a call to
phy_get from a driver where the use of a phy is optional.

Rather then adding all sort of complicated checks for this, and/or adding
special functions like devm_phy_get_optional, simply don't log an error,
and let deciding if get_phy returning an error really should result in a
dev_err up to the caller.

Signed-off-by: Hans de Goede 
Signed-off-by: Kishon Vijay Abraham I 
Signed-off-by: Greg Kroah-Hartman

drivers: phy: Add support for optional phys

2014-02-05T05:48:43+00:00

Add devm_phy_optional_get and phy_optional_get, which should be used
when the phy is optional. They does not return an error when the phy
does not exist, rather they returns NULL, which is considered as a valid
phy, but results in NOPs when used with the consumer API.

Signed-off-by: Andrew Lunn 
Tested-by: Gregory CLEMENT 
Acked-by: Kishon Vijay Abraham I 
Signed-off-by: Jason Cooper