On 02/05/2023 12:37, Stanley Chang[昌育德] wrote: > Hi Krzysztof, > >>>>>> On 02/05/2023 07:04, Stanley Chang wrote: >>>>>>> Add a new compatible name 'snps,dwc3-rtk-soc' of DT for realtek >>>>>>> dwc3 core to adjust the global register start address >>>>>>> >>>>>>> The RTK DHC SoCs were designed, the global register address offset >>>>>>> at >>>>>> >>>>>> What are: "RTK" and "DHC"? These are manufactured by Synopsys as >>>>>> you suggest in the patch? >>>>> >>>>> RTK is Realtek. >>>>> DHC is the department name in Realtek and the abbreviation of the >>>>> Digital >>>> Home Center. >>>>> The USB controller of RTK DHC SoCs used the DWC3 IP of Synopsys. >>>> >>>> Then entire compatible is not correct. Vendor is Realtek not Synopsys. >>>> DHC is not even device name. Use real device names. >>> >>> So, can we use the compatible name as 'realtek,dwc3' ? >> >> dwc3 is not a real device name for Realtek. > > We still use dwc3 IP in Realtek's SoC. Why is the name "dwc3" inappropriate? dwc3 is the name of design coming from Synopsys. Your device is probably called differently. Why it is inappropriate? Because your device is not called DWC3, even though you use IP from Synopsys. Although vendor,dwc3 is already used as compatible in several cases, I don't think it is a good pattern. > > Should compatibility names use the SoC name? > For example, our SoC name > RTD129x, RTD139x, RTD161x, RTD161xB, etc. > Should we use these names in compatible names? > "realtek, rtd129x", "realtek, rtd139x", "realtek, rtd161x"...etc. Regular rules apply, because your device is not special. https://elixir.bootlin.com/linux/v6.1-rc1/source/Documentation/devicetree/bindings/writing-bindings.rst#L42 Therefore either SoC-based device specific name or followed by: 1. SoC-based device specific fallback, 2. Family-device generic fallback, Best regards, Krzysztof
