diff options
| author | Douglas Anderson <dianders@chromium.org> | 2017-09-22 19:44:06 +0300 |
|---|---|---|
| committer | Kishon Vijay Abraham I <kishon@ti.com> | 2017-10-23 08:49:25 +0300 |
| commit | e023b1fb5286e23c224f2ae312831a4fce258c02 (patch) | |
| tree | 3fba297ce3665b81492c93b9b2c17e6f35a510ff /drivers/phy/allwinner | |
| parent | f85fd4c909565892a49337ef482090e446c4e5bd (diff) | |
| download | linux-e023b1fb5286e23c224f2ae312831a4fce258c02.tar.xz | |
phy: rockchip-typec: Do the calibration more correctly
Calculate the calibration code as per the docs. The docs talk about
reading and averaging the pullup and pulldown calibration codes. They
also talk about adding in some adjustment codes. Let's do what the
docs say.
In practice this doesn't seem to matter a whole lot. On a device I
tested the pullup and pulldown codes were nearly the same (0x23 and
0x24) and the adjustment codes were 0.
Reviewed-by: Chris Zhong <zyw@rock-chips.com>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Diffstat (limited to 'drivers/phy/allwinner')
0 files changed, 0 insertions, 0 deletions