Lines Matching refs:phy

18 all over the Linux kernel to drivers/phy to increase code re-use and for
56 struct phy *phy_create(struct device *dev, struct device_node *node,
58 struct phy *devm_phy_create(struct device *dev, struct device_node *node,
62 the device pointer and phy ops.
66 Inorder to dereference the private data (in phy_ops), the phy provider driver
75 struct phy *phy_get(struct device *dev, const char *string);
76 struct phy *phy_optional_get(struct device *dev, const char *string);
77 struct phy *devm_phy_get(struct device *dev, const char *string);
78 struct phy *devm_phy_optional_get(struct device *dev, const char *string);
79 struct phy *devm_of_phy_get_by_index(struct device *dev, struct device_node *np,
84 should contain the phy name as given in the dt data and in the case of
89 devm_phy_optional_get should be used when the phy is optional. These
91 the phy cannot be found.Some generic drivers, such as ehci, may use multiple
92 phys and for such drivers referencing phy(s) by name(s) does not make sense. In
93 this case, devm_of_phy_get_by_index can be used to get a phy reference based on
96 It should be noted that NULL is a valid phy reference. All phy
97 consumer calls on the NULL phy become NOPs. That is the release calls,
99 phy_power_off() calls are all NOP when applied to a NULL phy. The NULL
100 phy is useful in devices for handling optional phy devices.
108 void phy_put(struct phy *phy);
109 void devm_phy_put(struct device *dev, struct phy *phy);
119 void phy_destroy(struct phy *phy);
120 void devm_phy_destroy(struct device *dev, struct phy *phy);
128 pm_runtime_enable of the phy device created by this subsystem is called and
129 while destroying the PHY, pm_runtime_disable is called. Note that the phy
146 the struct phy already exists.
151 int phy_create_lookup(struct phy *phy, const char *con_id, const char *dev_id);
152 void phy_remove_lookup(struct phy *phy, const char *con_id, const char *dev_id);
157 Documentation/devicetree/bindings/phy/phy-bindings.txt