devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Abel Vesa <abel.vesa@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: x1e80100-crd: Add pmic-glink node with all 3 connectors
Date: Mon, 3 Jun 2024 12:02:17 +0200	[thread overview]
Message-ID: <Zl2UqbmqR5KLtUXS@hovoldconsulting.com> (raw)
In-Reply-To: <Zl2SHA9o1kUMMnOa@hovoldconsulting.com>

On Mon, Jun 03, 2024 at 11:51:24AM +0200, Johan Hovold wrote:
> On Mon, Jun 03, 2024 at 11:49:04AM +0200, Johan Hovold wrote:
> > On Mon, Jun 03, 2024 at 11:26:28AM +0200, Johan Hovold wrote:
> 
> > > [   10.730571] ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: invalid connector number, ignoring
> > > [   10.730656] pmic_glink_altmode.pmic_glink_altmode pmic_glink.altmode.0: invalid connector number, ignoring
> > 
> > Ok, it's just the pmic ucsi driver that is hardcoding max two ports
> > still. I'll send a fix.
> 
> Abel had already sent a fix for the above here:
> 
> 	https://lore.kernel.org/lkml/20240527-x1e80100-soc-qcom-pmic-glink-v1-1-e5c4cda2f745@linaro.org/

Nope, sorry, the above was for the PMIC GLINK driver itself. I just sent
a corresponding update for the GLINK UCSI driver here:

	https://lore.kernel.org/all/20240603100007.10236-1-johan+linaro@kernel.org/
 
> The PPMI init failure still remains, though:
> 
> 	ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: PPM init failed, stop trying

Johan

  reply	other threads:[~2024-06-03 10:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  8:07 [PATCH 0/3] arm64: dts: qcom: x1e80100: Describe 3 USB Type-C connectors currently used Abel Vesa
2024-05-27  8:07 ` [PATCH 1/3] arm64: dts: qcom: x1e80100: Add ports nodes to USB1 SS[0-2] PHYs and controllers Abel Vesa
2024-05-27  9:22   ` Dmitry Baryshkov
2024-05-28 12:23   ` Konrad Dybcio
2024-05-27  8:07 ` [PATCH 2/3] arm64: dts: qcom: x1e80100-crd: Add pmic-glink node with all 3 connectors Abel Vesa
2024-05-27  9:25   ` Dmitry Baryshkov
2024-05-28 12:28   ` Konrad Dybcio
2024-05-28 13:09     ` Dmitry Baryshkov
2024-06-03  8:48   ` Johan Hovold
2024-06-03  8:49     ` Dmitry Baryshkov
2024-06-03  9:26       ` Johan Hovold
2024-06-03  9:47         ` Dmitry Baryshkov
2024-06-03  9:49         ` Johan Hovold
2024-06-03  9:50           ` Dmitry Baryshkov
2024-06-03  9:51           ` Johan Hovold
2024-06-03 10:02             ` Johan Hovold [this message]
2024-05-27  8:07 ` [PATCH 3/3] arm64: dts: qcom: x1e80100-qcp: " Abel Vesa
2024-05-27  9:26   ` Dmitry Baryshkov

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=Zl2UqbmqR5KLtUXS@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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).