diff options
author | Kishon Vijay Abraham I <kishon@ti.com> | 2014-07-14 15:55:02 +0530 |
---|---|---|
committer | Kishon Vijay Abraham I <kishon@ti.com> | 2014-07-22 12:46:11 +0530 |
commit | f0ed817638b59aa927f1f7e9564dd8796b18dc4f (patch) | |
tree | 8d33a1dc9b780a2413565d80a19b649b056fb4cd /Documentation | |
parent | 2a4c37016ca96e413cd352985d3a0db8cfb7716c (diff) | |
download | linux-f0ed817638b59aa927f1f7e9564dd8796b18dc4f.tar.bz2 |
phy: core: Let node ptr of PHY point to PHY and not of PHY provider
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 <kishon@ti.com>
Acked-by: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/phy.txt | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/Documentation/phy.txt b/Documentation/phy.txt index ebff6ee52441..c6594af94d25 100644 --- a/Documentation/phy.txt +++ b/Documentation/phy.txt @@ -53,10 +53,12 @@ unregister the PHY. The PHY driver should create the PHY in order for other peripheral controllers to make use of it. The PHY framework provides 2 APIs to create the PHY. -struct phy *phy_create(struct device *dev, const struct phy_ops *ops, - struct phy_init_data *init_data); -struct phy *devm_phy_create(struct device *dev, const struct phy_ops *ops, - struct phy_init_data *init_data); +struct phy *phy_create(struct device *dev, struct device_node *node, + const struct phy_ops *ops, + struct phy_init_data *init_data); +struct phy *devm_phy_create(struct device *dev, struct device_node *node, + const struct phy_ops *ops, + struct phy_init_data *init_data); The PHY drivers can use one of the above 2 APIs to create the PHY by passing the device pointer, phy ops and init_data. |