On 05/07/2022 15:19, Han Xu wrote: >>>>> + nxp,fspi-dll-slvdly: >>>>> + $ref: /schemas/types.yaml#/definitions/uint32 >>>>> + description: | >>>>> + Specify the DLL slave line delay value. >>>> >>>> What are the units? >>> >>> Do you mean here need to give more detail explain about this properity? >>> >>> How about change like this? >>> Specify the DLL slave line delay value. The delay target for slave delay line is: >> ((nxp,fspi-dll-slvdly+1) * 1/32 * clock cycle of reference clock (serial root clock). >> >> This would be good. >> >>> The range of this value is 0~16. >> >> This needs to go to schema instead as "maximum: 16". >> >> But still the question is - what are the units used in this "delay"? ms? us? > > HI Krzysztof, > > According to the formula, the range should be 0~15, 16 should do nothing or no delay. Sure, just add some constraint. > > The unit should be clock phase. In other words, the delay can be in range of 1/32~1/2 clock cycle. So we probably misunderstood each other... looking at the driver it also explains the confusing. You encoded here register value which is pretty often wrong approach. This should be instead meaningful value for the user of the bindings, so usually using one of property units: https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/property-units.yaml I think you could use here clock cycles or clock phase, but then it has to be obvious it is that unit. Best regards, Krzysztof
