12 May, 2015
1 commit
-
Some generic drivers, such as ehci, may use multiple phys and for such
drivers referencing phy(s) by name(s) does not make sense. Instead of
inventing new naming schemes and using custom code to iterate through them,
such drivers are better of using nameless phy bindings and using this newly
introduced API to iterate through them.Signed-off-by: Arun Ramamurthy
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
[kishon@ti.com: fix compilation errors]
Signed-off-by: Kishon Vijay Abraham I
21 Nov, 2014
1 commit
-
Separates registration of the phy and the lookup. The method
is copied from clkdev.c,Signed-off-by: Heikki Krogerus
Signed-off-by: Kishon Vijay Abraham I
22 Jul, 2014
1 commit
-
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
05 Feb, 2014
2 commits
-
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 -
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.Signed-off-by: Andrew Lunn
Tested-by: Gregory CLEMENT
Acked-by: Kishon Vijay Abraham I
Signed-off-by: Jason Cooper
28 Sep, 2013
1 commit
-
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.PHY drivers should create the PHY by passing id and ops like init, exit,
power_on and power_off. This framework is also pm runtime enabled.The documentation for the generic PHY framework is added in
Documentation/phy.txt and the documentation for dt binding can be found at
Documentation/devicetree/bindings/phy/phy-bindings.txtCc: Tomasz Figa
Cc: Greg Kroah-Hartman
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Felipe Balbi
Tested-by: Sylwester Nawrocki
Signed-off-by: Greg Kroah-Hartman