From: Vinod Koul <vkoul@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v4 0/3] Add USB/DP combo PHY config for SM6350
Date: Thu, 2 Feb 2023 18:49:44 +0530 [thread overview]
Message-ID: <Y9u4cAK+uKXuu+uL@matsya> (raw)
In-Reply-To: <20230120-sm6350-usbphy-v4-0-4d700a90ba16@fairphone.com>
On 23-01-23, 14:29, Luca Weiss wrote:
> While this patchset started out as just adding a dedicated init sequence
> for SM6350 since USB PHY init didn't work in some cases, now it's also
> migrating the phy config and dts over to a new format.
>
> Also note, that the DP portions are pratically untested since TCPM
> (type-C port manager) and possibly other components aren't brought up
> yet.
Applied 1-2, thanks
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
cover doesnt need sob :)
> ---
> Changes in v4:
> - Fix dp_serdes offsets in driver, add dp_txa & dp_txb fields (as in v2)
> - Fix order of resets in dtsi
> - Link to v3: https://lore.kernel.org/r/20221130081430.67831-1-luca.weiss@fairphone.com
>
> ---
> Luca Weiss (3):
> dt-bindings: phy: qcom,qmp-usb3-dp: Add sm6350 compatible
> phy: qcom-qmp-combo: Add config for SM6350
> arm64: dts: qcom: sm6350: Use specific qmpphy compatible
>
> .../phy/qcom,sc8280xp-qmp-usb43dp-phy.yaml | 1 +
> arch/arm64/boot/dts/qcom/sm6350.dtsi | 54 +++-----
> drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 139 ++++++++++++++++++++-
> 3 files changed, 154 insertions(+), 40 deletions(-)
> ---
> base-commit: d514392f17fd4d386cfadde7f849d97db4ca1fb0
> change-id: 20230120-sm6350-usbphy-87c5e3f0218e
>
> Best regards,
> --
> Luca Weiss <luca.weiss@fairphone.com>
--
~Vinod
next prev parent reply other threads:[~2023-02-02 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 13:29 [PATCH v4 0/3] Add USB/DP combo PHY config for SM6350 Luca Weiss
2023-01-23 13:29 ` [PATCH v4 1/3] dt-bindings: phy: qcom,qmp-usb3-dp: Add sm6350 compatible Luca Weiss
2023-01-23 13:29 ` [PATCH v4 2/3] phy: qcom-qmp-combo: Add config for SM6350 Luca Weiss
2023-01-23 14:06 ` Johan Hovold
2023-01-23 13:29 ` [PATCH v4 3/3] arm64: dts: qcom: sm6350: Use specific qmpphy compatible Luca Weiss
2023-01-23 16:26 ` Konrad Dybcio
2023-02-02 13:19 ` Vinod Koul [this message]
2023-02-02 13:39 ` [PATCH v4 0/3] Add USB/DP combo PHY config for SM6350 Luca Weiss
2023-02-02 18:40 ` Konstantin Ryabitsev
2023-02-09 4:23 ` (subset) " Bjorn Andersson
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=Y9u4cAK+uKXuu+uL@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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