[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d7072a11-10c0-47ee-9cad-e64654fbb018@kernel.org>
Date: Tue, 7 Oct 2025 10:47:11 +0900
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Wesley Cheng <wesley.cheng@....qualcomm.com>, krzk+dt@...nel.org,
conor+dt@...nel.org, konrad.dybcio@....qualcomm.com,
dmitry.baryshkov@....qualcomm.com, kishon@...nel.org, vkoul@...nel.org,
gregkh@...uxfoundation.org, robh@...nel.org
Cc: linux-arm-msm@...r.kernel.org, linux-phy@...ts.infradead.org,
linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 00/10] Introduce Glymur USB support
On 07/10/2025 10:05, Wesley Cheng wrote:
>
>
> On 10/6/2025 6:02 PM, Krzysztof Kozlowski wrote:
>> On 07/10/2025 07:19, Wesley Cheng wrote:
>>> This series enables the PHY level changes that are required to support
>>> the type C based controllers and the multiport controller. The typeC
>>> ports utilize a usb43dp based QMP PHY for the SSUSB path, while using
>>> the M31 eUSB2 PHY for the HSUSB path. For the multiport controller,
>>> it will utilize two QMP UNI PHYs for the SSUSB path, and two M31 eUSB2
>>> PHYs for the HSUSB path.
>>>
>>> -----
>>> Changes in v5:
>>> - Moved phy-qcom-qmp-usb43-pcs-v8.h into USB specific QMP driver
>>> - Fixed DT bindings for clock properties for QMP combo PHY
>>>
>>
>> Where are lore links? Why aren't you using b4?
>>
>
> Sorry, I'm confused? Lore links to what exactly? There aren't any
> dependencies here, in case you mixed up this series with the DT one.
Lore links to the previous versions. They are added automatically.
Best regards,
Krzysztof
Powered by blists - more mailing lists