From: Heiko Stuebner <heiko@sntech.de>
To: Da Xue <da@lessconfused.com>,
Christopher Obbard <chris.obbard@collabora.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Corentin Labbe <clabbe@baylibre.com>,
kernel <kernel@collabora.com>
Subject: Re: [PATCH] arm64: dts: rockchip: Enable TYPE-C PD for ROC-RK3399-PC
Date: Fri, 28 Jul 2023 20:30:02 +0200 [thread overview]
Message-ID: <4659362.yKVeVyVuyW@phil> (raw)
In-Reply-To: <8ec1c4bb97ba0857275a540590fb302929436ba4.camel@collabora.com>
Am Dienstag, 25. Juli 2023, 10:02:21 CEST schrieb Christopher Obbard:
> Hi Da, Jagan,
>
> On Tue, 2023-07-25 at 03:39 -0400, Da Xue wrote:
> > On Mon, Jul 24, 2023 at 9:55 AM Christopher Obbard
> > <chris.obbard@collabora.com> wrote:
> > >
> > > On Wed, 2023-07-19 at 17:51 +0530, Jagan Teki wrote:
> > > > The power supply circuit in ROC-RK3399-PC is
> > > >
> > > > Power Supply (or PPS) => FUSB => MP8859
> > > >
> > > > VUBS pin of FUSB and IN pin of MP8859 is supplied via TYPEC_IN.
> > > >
> > > > The MP8859 operated with 2.8V to 22V supply voltage and typical
> > > > applications this supply can be 12V.
> > > >
> > > > This patch is trying to support the PD by changing the FUSB VBUS supply
> > > > to 12V and tune the I2C7 timings from downstream kernel.
> > > >
> > > > Tested with PD3.0 PPS with supply voltages of 12V/3A and 20V/5A.
> > >
> > > Hi Jagan,
> > >
> > > This series works fine with a "dumb" (no PD negotiation) 5.1V Raspberry Pi PSU.
> > >
> > > It also works fine with a Dell 45W USB-C Laptop Power Supply (model AA45NM170) which provides 5V@3A,9V@3A,15V@3A,20V@2.25A, where Linux master fails and just tells the USB-PD PSU to power-off.
> >
> > I think this depends on the recent Rockchip TCPM changes. FUSB302 has
> > been a pain in the USB or else this platform would have launched a lot
> > longer ago.
>
> Sorry, I was testing this patch on top of next-20230724 which includes https://patchwork.kernel.org/project/linux-rockchip/list/?series=757752:
>
> 8be558dcffe69b078b34b1fa93b82acaf4ce4957 ("usb: typec: tcpm: add get max power support")
> 1e35f074399dece73d5df11847d4a0d7a6f49434 ("usb: typec: tcpm: fix cc role at port reset")
>
> Can you check if I am missing any other patches ?
so I guess the question is, are there any new clues and/or does this patch
make the situaton better or worse for the roc-rk3399-pc board as it stands
now.
Thanks
Heiko
next prev parent reply other threads:[~2023-07-28 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 12:21 [PATCH] arm64: dts: rockchip: Enable TYPE-C PD for ROC-RK3399-PC Jagan Teki
2023-07-24 13:55 ` Christopher Obbard
2023-07-25 7:39 ` Da Xue
2023-07-25 8:02 ` Christopher Obbard
2023-07-28 18:30 ` Heiko Stuebner [this message]
2023-07-28 18:45 ` Jagan Teki
2023-07-29 2:30 ` Frank Wang
2023-08-30 21:07 ` Da Xue
2023-09-22 23:14 ` Da Xue
2023-07-28 18:52 ` Jagan Teki
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=4659362.yKVeVyVuyW@phil \
--to=heiko@sntech.de \
--cc=chris.obbard@collabora.com \
--cc=clabbe@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=da@lessconfused.com \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
/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).