From: Jun Li <jun.li@nxp.com>
To: robh+dt@kernel.org, mark.rutland@arm.com,
gregkh@linuxfoundation.org, heikki.krogerus@linux.intel.com
Cc: a.hajda@samsung.com, jun.li@nxp.com, linux@roeck-us.net,
yueyao@google.com, shufan_lee@richtek.com, o_leveque@orange.fr,
linux-usb@vger.kernel.org, linux-imx@nxp.com
Subject: [v3,10/12] staging: typec: tcpci: keep the not connecting cc line open
Date: Tue, 13 Mar 2018 17:34:36 +0800 [thread overview]
Message-ID: <1520933678-10535-11-git-send-email-jun.li@nxp.com> (raw)
While set polarity, we should keep the not connecting cc line to be
open when attached.
Signed-off-by: Li Jun <jun.li@nxp.com>
---
drivers/staging/typec/tcpci.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/typec/tcpci.c b/drivers/staging/typec/tcpci.c
index 9a230c6..6fdb179 100644
--- a/drivers/staging/typec/tcpci.c
+++ b/drivers/staging/typec/tcpci.c
@@ -185,6 +185,7 @@ static int tcpci_set_polarity(struct tcpc_dev *tcpc,
enum typec_cc_polarity polarity)
{
struct tcpci *tcpci = tcpc_to_tcpci(tcpc);
+ unsigned int reg;
int ret;
ret = regmap_write(tcpci->regmap, TCPC_TCPC_CTRL,
@@ -193,7 +194,17 @@ static int tcpci_set_polarity(struct tcpc_dev *tcpc,
if (ret < 0)
return ret;
- return 0;
+ /* Set the not connected cc line open */
+ ret = regmap_read(tcpci->regmap, TCPC_ROLE_CTRL, ®);
+ if (ret < 0)
+ return ret;
+ if (polarity == TYPEC_POLARITY_CC2)
+ ret = TCPC_ROLE_CTRL_CC1_SHIFT;
+ else
+ ret = TCPC_ROLE_CTRL_CC2_SHIFT;
+ reg |= TCPC_ROLE_CTRL_CC_OPEN << ret;
+ reg &= ~TCPC_ROLE_CTRL_DRP;
+ return regmap_write(tcpci->regmap, TCPC_ROLE_CTRL, reg);
}
static int tcpci_set_vconn(struct tcpc_dev *tcpc, bool enable)
next reply other threads:[~2018-03-13 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 9:34 Jun Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-14 8:59 [v3,10/12] staging: typec: tcpci: keep the not connecting cc line open shufan_lee(李書帆)
2018-03-20 1:59 Jun Li
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=1520933678-10535-11-git-send-email-jun.li@nxp.com \
--to=jun.li@nxp.com \
--cc=a.hajda@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=o_leveque@orange.fr \
--cc=robh+dt@kernel.org \
--cc=shufan_lee@richtek.com \
--cc=yueyao@google.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;
as well as URLs for NNTP newsgroup(s).