diff for duplicates of <354d6100-311f-44d7-b8a5-1fd671b651e3@kernel.org> diff --git a/a/1.txt b/N1/1.txt index 2b847ef..8fd8647 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -62,46 +62,4 @@ On 02/03/2025 10:16, Ivaylo Ivanov wrote: >>> initialization can be done and USB2 works. If the USBCON phy is not set >>> up before the eUSB2 one, the device hangs, so there is definitely a >>> dependancy between them. For PIPE3 we'd need to control the pipe3 ->>> attaching/deattaching and then initialize the synopsys USBDP combophy. ->> Does it mean there is no USB DRD phy controller as before? ->> ->> Anyway the problem is you have DWC3 -> PHY -> PHY. Looks one phy too many. -> -> So... -> -> DWC3 -> USBDRD (USBCON) -> PHYs? - -No, drop last phy. You just wrote the same as me - two phys, because -usbdrd is the phy. In all existing designs there is no such controllable -object from the point of view of operating system. - -> -> ...with usbdrd controller connecting and controlling the USB2 and USB3 -> phys, as well as dual role mode? - -Yes. - -> Well, where is the DRD part in the exynos5 -> driver? - -DRD? I believe it is part of DWC3, the same as in every other standard -implementation of Synopsys DWC3. - -> -> I guess it does perfectly fit the job of a usbdrd controller then (if it -> even deals with DRD). But then again, this brings up two questions: -> 1. Should this driver even be named exynos2200-usbcon and not, for -> example, exynos2200-usbdrd? - -Are you sure we talk about the same thing? USBDRD is IP block in the -Exynos and a device driver. Call your device as appropriate it is - -based on datasheet or downstream sources. - -> 2. Are the exynos5-usbdrd phys really only USBDRD, or do they implement -> USB speed functionality? What is the UTMI/PIPE3 setup for then? - -Dunno, I don't get what you mean by "exynos5-usbdrd phys really only -USBDRD". USBDRD is just the name of the device. - -Best regards, -Krzysztof +>>> attaching/deattaching and then initialize the synopsys USBDP combophy diff --git a/a/content_digest b/N1/content_digest index b4fd8d8..c46f272 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -88,48 +88,6 @@ ">>> initialization can be done and USB2 works. If the USBCON phy is not set\n" ">>> up before the eUSB2 one, the device hangs, so there is definitely a\n" ">>> dependancy between them. For PIPE3 we'd need to control the pipe3\n" - ">>> attaching/deattaching and then initialize the synopsys USBDP combophy.\n" - ">> Does it mean there is no USB DRD phy controller as before?\n" - ">>\n" - ">> Anyway the problem is you have DWC3 -> PHY -> PHY. Looks one phy too many.\n" - "> \n" - "> So...\n" - "> \n" - "> DWC3 -> USBDRD (USBCON) -> PHYs?\n" - "\n" - "No, drop last phy. You just wrote the same as me - two phys, because\n" - "usbdrd is the phy. In all existing designs there is no such controllable\n" - "object from the point of view of operating system.\n" - "\n" - "> \n" - "> ...with usbdrd controller connecting and controlling the USB2 and USB3\n" - "> phys, as well as dual role mode?\n" - "\n" - "Yes.\n" - "\n" - "> Well, where is the DRD part in the exynos5\n" - "> driver?\n" - "\n" - "DRD? I believe it is part of DWC3, the same as in every other standard\n" - "implementation of Synopsys DWC3.\n" - "\n" - "> \n" - "> I guess it does perfectly fit the job of a usbdrd controller then (if it\n" - "> even deals with DRD). But then again,\302\240 this brings up two questions:\n" - "> 1. Should this driver even be named exynos2200-usbcon and not, for\n" - "> example, exynos2200-usbdrd?\n" - "\n" - "Are you sure we talk about the same thing? USBDRD is IP block in the\n" - "Exynos and a device driver. Call your device as appropriate it is -\n" - "based on datasheet or downstream sources.\n" - "\n" - "> 2. Are the exynos5-usbdrd phys really only USBDRD, or do they implement\n" - "> USB speed functionality? What is the UTMI/PIPE3 setup for then?\n" - "\n" - "Dunno, I don't get what you mean by \"exynos5-usbdrd phys really only\n" - "USBDRD\". USBDRD is just the name of the device.\n" - "\n" - "Best regards,\n" - Krzysztof + >>> attaching/deattaching and then initialize the synopsys USBDP combophy -d2ece7c30288cf457649a7eb46c7b5b46edcd2037bd848522dfbaabfe971331d +3436d5ce3fa4b9a854ed6970433ebc9aa956b9b862b96cbca4e5517ffc8d114c
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox