diff options
author | Maxime Ripard <maxime.ripard@bootlin.com> | 2018-12-07 16:55:29 +0300 |
---|---|---|
committer | Kishon Vijay Abraham I <kishon@ti.com> | 2018-12-12 07:31:50 +0300 |
commit | aeaac93ddb28eeacc0dff9c12cb338eb1de7481d (patch) | |
tree | 9324e79bddac5a7cdff0d62582b16100f1aef2ea /include/linux/serial_bcm63xx.h | |
parent | c8457828ff481411dca4cdea944c1a0980c862e1 (diff) | |
download | linux-aeaac93ddb28eeacc0dff9c12cb338eb1de7481d.tar.xz |
phy: Add configuration interface
The phy framework is only allowing to configure the power state of the PHY
using the init and power_on hooks, and their power_off and exit
counterparts.
While it works for most, simple, PHYs supported so far, some more advanced
PHYs need some configuration depending on runtime parameters. These PHYs
have been supported by a number of means already, often by using ad-hoc
drivers in their consumer drivers.
That doesn't work too well however, when a consumer device needs to deal
with multiple PHYs, or when multiple consumers need to deal with the same
PHY (a DSI driver and a CSI driver for example).
So we'll add a new interface, through two funtions, phy_validate and
phy_configure. The first one will allow to check that a current
configuration, for a given mode, is applicable. It will also allow the PHY
driver to tune the settings given as parameters as it sees fit.
phy_configure will actually apply that configuration in the phy itself.
Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Diffstat (limited to 'include/linux/serial_bcm63xx.h')
0 files changed, 0 insertions, 0 deletions