From: Krzysztof Kozlowski <krzk@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Peter Griffin" <peter.griffin@linaro.org>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH v2] phy: exynos5-usbdrd: Fix broken USB on Exynos5422 (TYPEC dependency)
Date: Mon, 17 Feb 2025 10:03:03 +0100 [thread overview]
Message-ID: <35d9c210-1ffb-4878-863c-912f389b18e5@kernel.org> (raw)
In-Reply-To: <88b00cc53cd5cb3682a29d6a2ec491c7640129ce.camel@linaro.org>
On 17/02/2025 06:59, André Draszik wrote:
> Hi Krzysztof,
>
> On Sun, 2025-02-16 at 12:41 +0100, Krzysztof Kozlowski wrote:
>> Older Exynos designs, like Exynos5422, do not have USB Type-C and the
>> USB DRD PHY does not really depend on Type-C for these devices at all.
>> Incorrectly added optional dependency on CONFIG_TYPEC caused this driver
>> to be missing for exynos_defconfig and as result Exynos5422-based boards
>> like Hardkernel Odroid HC1 failed to probe USB.
>>
>> However ARM64 boards should have CONFIG_TYPEC enabled and in proper
>> state (e.g. =y when PHY_EXYNOS5_USBDRD is =y) for proper USB support on
>> Google GS101 boards.
>>
>> Add itermediate CONFIG_PHY_EXYNOS5_USBDRD_TYPEC symbol to skip TYPEC on
>> older boards, while still expressing optional dependency.
>>
>> Reported-by: Krzysztof Kozlowski <krzk@kernel.org>
>> Closes: https://krzk.eu/#/builders/21/builds/6139
>> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> Closes: https://lore.kernel.org/all/3c0b77e6-357d-453e-8b63-4757c3231bde@samsung.com/
>> Fixes: 09dc674295a3 ("phy: exynos5-usbdrd: subscribe to orientation notifier if required")
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> ---
>>
>> Patch for issue in linux-next
>>
>> Changes in v2:
>> 1. Add PHY_EXYNOS5_USBDRD_TYPEC, so arm64 defconfig will have both
>> symbols in-sync
>> ---
>> drivers/phy/samsung/Kconfig | 12 +++++++++++-
>> drivers/phy/samsung/phy-exynos5-usbdrd.c | 1 +
>> 2 files changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/phy/samsung/Kconfig b/drivers/phy/samsung/Kconfig
>> index 7fba571c0e2b..b20ac6b75993 100644
>> --- a/drivers/phy/samsung/Kconfig
>> +++ b/drivers/phy/samsung/Kconfig
>> @@ -77,12 +77,22 @@ config PHY_S5PV210_USB2
>> particular SoC is compiled in the driver. In case of S5PV210 two phys
>> are available - device and host.
>>
>> +# None of ARM32 Samsung boards use Type-C, however newer ARM64 do and
>> +# PHY_EXYNOS5_USBDRD driver needs TYPEC to be in a matching state to avoid link
>> +# failures (see optional dependencies in kconfig-language.rst). Intermediate
>> +# PHY_EXYNOS5_USBDRD_TYPEC symbol allows to skip TYPEC on ARM32 boards.
>> +config PHY_EXYNOS5_USBDRD_TYPEC
>> + tristate
>> + depends on ARCH_EXYNOS
>> + depends on ARM || TYPEC || !TYPEC
>> + default y
>> +
>> config PHY_EXYNOS5_USBDRD
>> tristate "Exynos5 SoC series USB DRD PHY driver"
>> depends on (ARCH_EXYNOS && OF) || COMPILE_TEST
>> depends on HAS_IOMEM
>> - depends on TYPEC || (TYPEC=n && COMPILE_TEST)
>
> Is it not possible to just drop the '&& COMPILE_TEST' part to make
> it
> depends on TYPEC || TYPEC=n
> or
> depends on TYPEC || !TYPEC
> (without any of the other changes)?
>
> If not, why not, are there corner cases that doesn't catch? Some
> minimal testing seems to suggest that that works, too.
Yeah, I think I overcomplicated it. I wanted to make it really
independent from TYPEC on ARM, but that's not trivial and my patch fails
here.
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2025-02-17 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 11:41 [PATCH v2] phy: exynos5-usbdrd: Fix broken USB on Exynos5422 (TYPEC dependency) Krzysztof Kozlowski
2025-02-16 11:45 ` Krzysztof Kozlowski
2025-02-17 5:59 ` André Draszik
2025-02-17 9:03 ` Krzysztof Kozlowski [this message]
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=35d9c210-1ffb-4878-863c-912f389b18e5@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=kishon@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=peter.griffin@linaro.org \
--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