On Tue, Aug 23, 2022 at 03:03:51PM +0300, Krzysztof Kozlowski wrote: > On 23/08/2022 14:45, Serge Semin wrote: > > On Tue, Aug 23, 2022 at 11:44:16AM +0300, Krzysztof Kozlowski wrote: > >> On 23/08/2022 11:32, Serge Semin wrote: > >>> On Tue, Aug 23, 2022 at 11:17:23AM +0300, Krzysztof Kozlowski wrote: > >>>> On 22/08/2022 22:07, Serge Semin wrote: > >>>>> The Zynq A05 DDRC controller has nothing in common with DW uMCTL2 DDRC: > >>>>> the CSRs layout is absolutely different and it doesn't has IRQ unlike DW > >>>>> uMCTL2 DDR controller of all versions (v1.x, v2.x and v3.x). Thus there is > >>>>> no any reason to have these controllers described by the same bindings. > >>>>> Thus let's split them up. > >>>>> > >>>>> While at it rename the original Synopsys uMCTL2 DT-schema file to a more > >>>>> descriptive - snps,dw-umctl2-ddrc.yaml and add a more detailed title and > >>>>> description of the device bindings. > >>>> > >>> > > > >>>> Filename should be based on compatible, so if renaming then > >>>> snps,ddrc-3.80a.yaml or snps,ddrc.yaml... which leads to original > >>>> filename anyway. Therefore nack for rename. > > > > Original name was synopsys,ddrc-ecc.yaml which doesn't match any of > > the compatible strings. > > > >>> > >>> New requirement? I've submitted not a single patch to the DT-bindings > >>> sources and didn't get any comment from Rob about that. > >> > > > >> This is not a new requirement. It has been since some time and Rob gave > >> such reviews. > >> > >> https://lore.kernel.org/linux-devicetree/YlhkwvGdcf4ozTzG@xxxxxxxxxxxxxxxxxx/ > > > > April 2022. So it's new. It would be nice to have it defined somewhere > > in docs (writing-bindings.rst?). So does the compatibles order (this > > was surprising to me too). > > > >> > >> For devices with multiple compatibles that's a bit tricky, but assuming > >> the bindings describe both original design from Synopsys and it's > >> implementations, then something closer to Synopsys makes sense. > > > > The closest name would be snps,dw-umctl2-ddrc.yaml. snps,ddrc is too > > generic especially for the IP-cores vendor. It doesn't have a > > reference to the actual IP-core the device in subject is based on. > > You are aware that in such case mistake is not in the file name but in > the compatible? Let's compare, what is defined for Synopsys DW uMCTL2 DDRC in the DT-bindings now: compatible string: snps,ddrc-3.80a file name: synopsys,ddrc-ecc.yaml First of all they don't match at all. Secondly none of the names refer to the actual IP-core the DT-bindings file is defined for. So in this case the problem is in both: 1. file name has undefined vendor-prefix. It's supposed to be "snps". 2. file name has "ecc" suffix, which is a device property, but has nothing to do with the device actual name. 2. actual device name is different. It's DW uMCTL2 DDRC. Just DDRC doesn't identify the IP-core in subject. > > > > >> > >> > >>> In addition > >>> There are DT bindings with names different from what is defined in the > >>> compatible name. Moreover there are tons of bindings with various > >>> compatible names. What name to choose then? Finally the current name > >>> is too generic to use for actual DW uMCTL2 DDRC controller. > >> > > > >> There are thousands of bugs, inconsistencies, naming differences in > >> kernel. I don't find these as arguments to repeat the practice...so the > >> bindings file name should be based on the compatible. > > > > Did I ask for an exception? I justified why the renaming was necessary. You > > said it goes against the practice of having the DT-schema named as the > > device compatible strings and just nacked. But above in this message you said > > > >> "assuming the bindings describe both original design from Synopsys > >> and it's implementations, then something closer to Synopsys makes sense" > > > > What I suggest makes more sense than some abstract Synopsys DDRC, > > which may refer to a Synopsys DDR controller other than the subject > > one. So I see two solutions here: > > 1. Adding a new generic compatible string like "snps,dw-umctl2-ddrc" > > and deprecate the "snps,ddrc-3.80a". > > This might be good idea, although unfortunately replacing compatibles > takes quite a lot of time if you do not want to break any out-of-tree > users (read: other users of bindings). Well, I didn't imply the replacement, but "deprecation". It means to just mark the "snps,ddrc-3.80a" compatible string as deprecated in the bindings file and define a new one "snps,dw-umctl2-ddrc" which wouldn't have the "deprecated: true" property set. It shall at least implicitly warn people not to add new DTS-files with the deprecated device name. As I see it eventually the dtbs-check tool will be updated to auto-detect such attempts and, for instance, print a warning. > > > > It gets to be even more justified > > seeing the Synopsys IP-core version has been exported in the device > > CSRs since IP-core v3.20a. So having the version attached to the > > compatible string was absolutely redundant. > > The version might have sense in a way to differentiate from some older > versions, pre 3.20a. I've almost fully refactored the device driver, and can say for sure that the driver doesn't implement any Synopsys IP-core versions specifics: 1. "xlnx,zynq-ddrc-a05" - has absolutely nothing in common with the Synopsys DW uMCTL2 DDR controller (see the patch log for details). That's why I've split the driver and DT-bindings up. 2. "xlnx,zynqmp-ddrc-2.40a" - ZynqMP DDR controller based on the Synopsys uMCTL2 DDRC v2.40a. The device name is vendor-specific anyway. So seeing there is no any other ZynqMP DDR controller added, having IP-core version attached to the compatible string has been redundant in the first place. Anyway the driver implements only the ZynqMP-platform specifics irrespective to the IP-core version. 3. "snps,ddrc-3.80a" - without my patchsets this represents a Synopsys DW uMCTL2 DDR controller synthesized with 64-bit DQ-bus and 8xSDRAM words burst config. The later settings have nothing to do with the IP-core version, meanwhile what is really v3.x-specific isn't implemented in the driver. > The binding was probably incomplete anyway. At the current state it's incomplete indeed. After applying all my DT-related patches it will get to be almost complete, at least in the CSRs, IRQs, clocks and resets resources part. There is always room for the device-specific properties though, but judging by my experience caught from Rob' reviews such properties aren't welcome if we have the IP-core version detectable and if we can add the platform-specific compatible string. The later one could be used to define the platform-specific parameters right in the driver so the DT-bindings could be kept relatively simple. > > > > 2. Just deprecate the generic compatible string, the new compatible > > devices will be supposed to use a vendor-specific compatible strings, > > but still rename the DT-bindings file. This makes sense since the > > current generic name isn't quiet well structured. It' prefix-part is > > too generic and at the same time it refers to a device reversion for > > no much reason. > > You mean disallow entirely "snps,ddrc-3.80a" and expect everyone to use > device/implementation specific compatible? Yes as an alternative to the solution 1. described above. > I guess this depends whether > this custom block can be used without vendor specific addons. For > several other DW blocks we expect to have the generic snsp fallback and > this generic fallback can be used alone in Linux (pcie-designware-plat.c > binds to it). Just recently I've got a very long discussion with Rob regarding the generic fallback compatible string. What he said "drop the generic compatible fallback string. It proved to be useless." So I had to drop the generic fallback compatible string from the nodes of my local DTS files where it was appropriate and update all my DT-related patches to disallow having vendor-specific and generic compatible strings specified together. Note what Rob said concerned the generic compatible "fallback" case, not the generic compatible string in general. It's ok to have a generic device name defined irrespective to the platform vendor. Moreover it's applicable in case of the DW uMCTL2 DDRC IP-core since first IP-core version is auto-detectable starting from v3.20a and second I managed to implement auto-detection solutions for almost all the DDR/ECC-specific parameters. So I am more inclined to the solution 1) suggested by me in the previous email message: - deprecate "snps,ddrc-3.80a" string. - add new generic "snps,dw-umctl2-ddrc" compatible string. - rename the DT-bindings file. > > Here the Linux driver also binds to generic synopsys compatible, so I > would assume it has a meaning and use case on its own. Please see my messages above regarding the current Synopsys DW uMCTL2 EDAC driver implementation. > > > > > What do you think? > > > > * Note I've got it you'd prefer the renaming being performed in a > > separate patch. > > The rename could be in the split patch as here, but then I assume the > rename part to be detected by git and be a pure rename. However: > 1. The git did not mark it as rename (you might need to use custom > arguments to -M/-B/-C), Of course git hasn't detected it as rename, because aside with renaming I've split the bindings up. Splitting these two updates up into two patches will give us what you said. So to speak I suggest the next updates for v2: PATCH X. Detach the Zynq A05 DDRC DT-bindings to a separate schema. PATCH X + 1. Rename the Synopsys DW uMCTL2 DDRC bindings file and add a more descriptive generic compatible string name. What do you think? > 2. There were also changes in the process (allOf:if:then). Right. But this is in another patchset. I'll address your notes in there. -Sergey > > > Best regards, > Krzysztof
