From: Kishon Vijay Abraham I <kishon@ti.com>
To: Douglas Anderson <dianders@chromium.org>, <heiko@sntech.de>,
<zyw@rock-chips.com>
Cc: <groeck@chromium.org>, <shawnn@chromium.org>,
<dnschneid@chromium.org>, <linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 4/4] phy: rockchip-typec: Do the calibration more correctly
Date: Wed, 18 Oct 2017 16:49:27 +0530 [thread overview]
Message-ID: <e357cfd7-b5a3-29d8-02d7-2bf75a05aa19@ti.com> (raw)
In-Reply-To: <20170922164406.27606-5-dianders@chromium.org>
On Friday 22 September 2017 10:14 PM, Douglas Anderson wrote:
> 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>
merged the 3rd and 4th patch to next. Thanks!
-Kishon
> ---
>
> Changes in v3: None
> Changes in v2:
> - Removed extra blank line.
>
> drivers/phy/rockchip/phy-rockchip-typec.c | 27 ++++++++++++++++++---------
> 1 file changed, 18 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/phy/rockchip/phy-rockchip-typec.c b/drivers/phy/rockchip/phy-rockchip-typec.c
> index 95f8f23676b4..a96635447d48 100644
> --- a/drivers/phy/rockchip/phy-rockchip-typec.c
> +++ b/drivers/phy/rockchip/phy-rockchip-typec.c
> @@ -560,24 +560,33 @@ static void tcphy_dp_aux_calibration(struct rockchip_typec_phy *tcphy)
> u16 val;
> u16 tx_ana_ctrl_reg_1;
> u16 tx_ana_ctrl_reg_2;
> - s32 pu_calib_code;
> -
> - /* disable txda_cal_latch_en for rewrite the calibration values */
> - tx_ana_ctrl_reg_1 = readl(tcphy->base + TX_ANA_CTRL_REG_1);
> - tx_ana_ctrl_reg_1 &= ~TXDA_CAL_LATCH_EN;
> - writel(tx_ana_ctrl_reg_1, tcphy->base + TX_ANA_CTRL_REG_1);
> + s32 pu_calib_code, pd_calib_code;
> + s32 pu_adj, pd_adj;
> + u16 calib;
>
> /*
> - * read a resistor calibration code from CMN_TXPUCAL_CTRL[5:0] and
> - * write it to TX_DIG_CTRL_REG_2[5:0].
> + * Calculate calibration code as per docs: use an average of the
> + * pull down and pull up. Then add in adjustments.
> */
> val = readl(tcphy->base + CMN_TXPUCAL_CTRL);
> pu_calib_code = CMN_CALIB_CODE_POS(val);
> + val = readl(tcphy->base + CMN_TXPDCAL_CTRL);
> + pd_calib_code = CMN_CALIB_CODE_POS(val);
> + val = readl(tcphy->base + CMN_TXPU_ADJ_CTRL);
> + pu_adj = CMN_CALIB_CODE(val);
> + val = readl(tcphy->base + CMN_TXPD_ADJ_CTRL);
> + pd_adj = CMN_CALIB_CODE(val);
> + calib = (pu_calib_code + pd_calib_code) / 2 + pu_adj + pd_adj;
> +
> + /* disable txda_cal_latch_en for rewrite the calibration values */
> + tx_ana_ctrl_reg_1 = readl(tcphy->base + TX_ANA_CTRL_REG_1);
> + tx_ana_ctrl_reg_1 &= ~TXDA_CAL_LATCH_EN;
> + writel(tx_ana_ctrl_reg_1, tcphy->base + TX_ANA_CTRL_REG_1);
>
> /* write the calibration, then delay 10 ms as sample in docs */
> val = readl(tcphy->base + TX_DIG_CTRL_REG_2);
> val &= ~(TX_RESCAL_CODE_MASK << TX_RESCAL_CODE_OFFSET);
> - val |= pu_calib_code << TX_RESCAL_CODE_OFFSET;
> + val |= calib << TX_RESCAL_CODE_OFFSET;
> writel(val, tcphy->base + TX_DIG_CTRL_REG_2);
> usleep_range(10000, 10050);
>
>
prev parent reply other threads:[~2017-10-18 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 16:44 [PATCH v3 0/4] phy: rockchip-typec: Set "flip" properly; some cleanups; fix swing Douglas Anderson
2017-09-22 16:44 ` [PATCH v3 1/4] phy: rockchip-typec: Set the AUX channel flip state earlier Douglas Anderson
2017-09-22 16:44 ` [PATCH v3 2/4] phy: rockchip-typec: Don't set the aux voltage swing to 400 mV Douglas Anderson
2017-09-22 16:44 ` [PATCH v3 3/4] phy: rockchip-typec: Avoid magic numbers + add delays in aux calib Douglas Anderson
2017-09-22 16:44 ` [PATCH v3 4/4] phy: rockchip-typec: Do the calibration more correctly Douglas Anderson
2017-10-18 11:19 ` Kishon Vijay Abraham I [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e357cfd7-b5a3-29d8-02d7-2bf75a05aa19@ti.com \
--to=kishon@ti.com \
--cc=dianders@chromium.org \
--cc=dnschneid@chromium.org \
--cc=groeck@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=shawnn@chromium.org \
--cc=zyw@rock-chips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®