From: Douglas Anderson <dianders@chromium.org> To: kishon@ti.com, heiko@sntech.de, zyw@rock-chips.com Cc: shawnn@chromium.org, dnschneid@chromium.org, Douglas Anderson <dianders@chromium.org>, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/3] phy: rockchip-typec: Set "flip" at the right time; some cleanups Date: Wed, 6 Sep 2017 13:51:58 -0700 [thread overview] Message-ID: <20170906205201.16207-1-dianders@chromium.org> (raw) When connecting to certain DP monitors it was observed that only one of the two orientations of the type C to DP cable would work. Debugging showed that the problem was that we needed to set the type C "flip" state earlier. Once we did this, problems went away. While trying to dig into this problem and some others, I found that the proper documentation for the Type C PHY was available to me. This allowed me to cleanup the magic numbers in the funtion that I was touching and also fix a few minor issues that (luckily) haven't caused any problems yet. For this series I've added Chris Zhong's Reviewed-by tags since he gave a +1 to nearly identical patches on the Chrome OS gerrit and I didn't think he'd mind me carrying his tag. If folks would rather I didn't do that, please yell. Douglas Anderson (3): phy: rockchip-typec: Set the AUX channel flip state earlier phy: rockchip-typec: Avoid magic numbers + add delays in aux calib phy: rockchip-typec: Do the calibration more correctly drivers/phy/rockchip/phy-rockchip-typec.c | 247 ++++++++++++++++++++++++------ 1 file changed, 202 insertions(+), 45 deletions(-) -- 2.14.1.581.gf28d330327-goog
WARNING: multiple messages have this Message-ID (diff)
From: dianders@chromium.org (Douglas Anderson) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/3] phy: rockchip-typec: Set "flip" at the right time; some cleanups Date: Wed, 6 Sep 2017 13:51:58 -0700 [thread overview] Message-ID: <20170906205201.16207-1-dianders@chromium.org> (raw) When connecting to certain DP monitors it was observed that only one of the two orientations of the type C to DP cable would work. Debugging showed that the problem was that we needed to set the type C "flip" state earlier. Once we did this, problems went away. While trying to dig into this problem and some others, I found that the proper documentation for the Type C PHY was available to me. This allowed me to cleanup the magic numbers in the funtion that I was touching and also fix a few minor issues that (luckily) haven't caused any problems yet. For this series I've added Chris Zhong's Reviewed-by tags since he gave a +1 to nearly identical patches on the Chrome OS gerrit and I didn't think he'd mind me carrying his tag. If folks would rather I didn't do that, please yell. Douglas Anderson (3): phy: rockchip-typec: Set the AUX channel flip state earlier phy: rockchip-typec: Avoid magic numbers + add delays in aux calib phy: rockchip-typec: Do the calibration more correctly drivers/phy/rockchip/phy-rockchip-typec.c | 247 ++++++++++++++++++++++++------ 1 file changed, 202 insertions(+), 45 deletions(-) -- 2.14.1.581.gf28d330327-goog
next reply other threads:[~2017-09-06 20:52 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-06 20:51 Douglas Anderson [this message] 2017-09-06 20:51 ` [PATCH 0/3] phy: rockchip-typec: Set "flip" at the right time; some cleanups Douglas Anderson 2017-09-06 20:51 ` [PATCH 1/3] phy: rockchip-typec: Set the AUX channel flip state earlier Douglas Anderson 2017-09-06 20:51 ` Douglas Anderson 2017-09-06 20:51 ` Douglas Anderson 2017-09-06 20:52 ` [PATCH 2/3] phy: rockchip-typec: Avoid magic numbers + add delays in aux calib Douglas Anderson 2017-09-06 20:52 ` Douglas Anderson 2017-09-06 20:52 ` [PATCH 3/3] phy: rockchip-typec: Do the calibration more correctly Douglas Anderson 2017-09-06 20:52 ` Douglas Anderson 2017-09-06 21:24 ` Doug Anderson 2017-09-06 21:24 ` Doug Anderson 2017-09-06 21:24 ` Doug Anderson
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=20170906205201.16207-1-dianders@chromium.org \ --to=dianders@chromium.org \ --cc=dnschneid@chromium.org \ --cc=heiko@sntech.de \ --cc=kishon@ti.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.