linux-kernel - Re: [PATCH v1 3/4] phy: samsung: add Exynos2200 SNPS eUSB2 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <065ea296-480c-4ac4-bb4a-0fc2915b59f1@kernel.org>
Date: Sun, 16 Feb 2025 14:19:35 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ivaylo Ivanov <ivo.ivanov.ivanov1@...il.com>,
 Vinod Koul <vkoul@...nel.org>, Kishon Vijay Abraham I <kishon@...nel.org>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Alim Akhtar <alim.akhtar@...sung.com>,
 Philipp Zabel <p.zabel@...gutronix.de>
Cc: linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
 linux-phy@...ts.infradead.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 3/4] phy: samsung: add Exynos2200 SNPS eUSB2 driver

On 16/02/2025 10:51, Ivaylo Ivanov wrote:
>>
>>>>  You need to
>>>> integrate the changes, not create duplicated driver.
>>> I can do that, but it would be come a bit cluttered, won't it? Depends on
>>> if we want to follow the current oem-provided initialization sequence, or
>>> try and fully reuse what we have in there.
>>
>> I think it duplicates a lot, so it won't be clutter. We have many
>> drivers having common code and per-variant ops.
> 
> So the approach to take here is to make a common driver?

For example: one common module and two modules per each soc, because I
assume some per-soc stuff might be needed. But maybe even these two
modules are not necessary and everything could be in one driver.


> 
> What about the current modelling scheme, as-in taking the phandle to
> the usbcon phy and handling it?

What about it? Did you look at the bindings of qcom snps eusb2? Are you
saying you do not have here repeater? If so, then this phy phandle might
not be correct.



Best regards,
Krzysztof