From: "Igor Belwon" <igor.belwon@mentallysanemainliners.org>
To: "Vinod Koul" <vkoul@kernel.org>
Cc: "Kishon Vijay Abraham I" <kishon@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2 0/2] USB PHY support for Exynos990 SoCs
Date: Wed, 14 May 2025 16:26:52 +0200 [thread overview]
Message-ID: <D9VYC98LJTR0.LJXYC1H0BAKA@mentallysanemainliners.org> (raw)
In-Reply-To: <aCRXgpD0Ld2W4lHE@vaman>
On Wed May 14, 2025 at 10:42 AM CEST, Vinod Koul wrote:
> On 20-04-25, 21:28, Igor Belwon wrote:
>> Hi all!
>>
>> This patchset adds support for the USB 2.0 PHY of the Exynos990 SoC.
>> This SoC has a combo PHY that supports highspeed, superspeed USB and
>> DisplayPort, however due to my inability to test the superspeed part of
>> the combo phy (device always enumerated as high-speed, even on the
>> vendor kernels/bootloaders) only the highspeed part is brought up.
>>
>> These changes have been tested and confirmed working (with the USB_ETH
>> gadget and telnet/ssh in a ramdisk) on a device from the hubble family
>> (x1s) and also a device from the canvas family (c1s).
>
> I am missing the dt patch, can you pls report the whole series if you
> would like me to review and apply this
Hi Vinod,
I've sent the DT series a while back (before resending). Usually I
propose DT changes through Krzysztof's tree. The patches are
unchanged (they will be resent unchanged when all usb and wdt
changes are merged).
Here is the patchset:
- on patchwork: https://patchwork.kernel.org/project/linux-samsung-soc/patch/20250217-exynos990-dt-changes-febuary-v1-2-99935218cbf4@mentallysanemainliners.org/
- on the mailing list archives: https://lore.kernel.org/all/20250217-exynos990-dt-changes-febuary-v1-2-99935218cbf4@mentallysanemainliners.org/
Best regards
- Igor
next prev parent reply other threads:[~2025-05-14 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 19:28 [PATCH v2 0/2] USB PHY support for Exynos990 SoCs Igor Belwon
2025-04-20 19:28 ` [PATCH v2 1/2] dt-bindings: phy: samsung,usb3-drd-phy: Add exynos990 compatible Igor Belwon
2025-04-20 19:28 ` [PATCH v2 2/2] phy: exynos5-usbdrd: Add support for the Exynos990 usbdrd phy Igor Belwon
2025-05-14 8:42 ` [PATCH v2 0/2] USB PHY support for Exynos990 SoCs Vinod Koul
2025-05-14 14:26 ` Igor Belwon [this message]
2025-05-15 8:20 ` Vinod Koul
2025-05-15 9:14 ` Krzysztof Kozlowski
2025-05-15 14:26 ` Igor Belwon
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=D9VYC98LJTR0.LJXYC1H0BAKA@mentallysanemainliners.org \
--to=igor.belwon@mentallysanemainliners.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robh@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=vkoul@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