Hi Julius, Thanks for the review. On 7/22/25 23:57, Julius Werner wrote:
Compatible strings can be either explicit vendor names and part numbers (e.g. elpida,ECB240ABACN), or generated strings of the form lpddrX-YY,ZZZZ where X is the LPDDR version, YY is the manufacturer IDWhen you say "in case of LPDDR" below, you should also change this line to take other cases into account. Maybe the best way to write this would be something like: ...or generated strings of a memory type dependent form. For LPDDR types, that form is lpddrX-YY,ZZZZ where X is [...same text...]. For DDR types, that form is ddrX-YY,ZZZZZ... where X is [...new definition for DDR types, based on what's available in SPD...].
Yes I agree and if there is no SPD I'll mention the datasheet of the memory chip.
revision-id: $ref: /schemas/types.yaml#/definitions/uint32-array description: - Revision IDs read from Mode Register 6 and 7. One byte per uint32 cell (i.e. <MR6 MR7>). + Revision IDs read from Mode Register 6 and 7 in case of LPDDR. + One byte per uint32 cell (i.e. <MR6 MR7>).If this doesn't exist for DDR, then rather than "in case of LPDDR" this should probably say something like "LPDDR only"?
It exists in case of DDR, but it is either in the SPD if the memory is DIMM like or in the datasheet for soldered memory chip.
density: $ref: /schemas/types.yaml#/definitions/uint32 description: - Density in megabits of SDRAM chip. Decoded from Mode Register 8. + Density in megabits of SDRAM chip. Decoded from Mode Register 8 in case of + LPDDR.Can you list here where in SPD density and I/O width are stored for the various DDR types?
I'll try to find the info and yes. Best regards, Clément
