On 04/07/2022 09:18, Geert Uytterhoeven wrote: > Hi Krzysztof, > > On Sun, Jul 3, 2022 at 8:35 PM Krzysztof Kozlowski > <krzysztof.kozlowski@xxxxxxxxxx> wrote: >> As suggested by Rob [1], I organized a bit bindings for SoC devices having >> similar purpose - chip identification. >> >> These sometimes are put under nvmem directory, although in that case the >> purpose is usually broader than just chipid. > > Thanks for your series! > >> dt-bindings: hwinfo: group Chip ID-like devices >> dt-bindings: hwinfo: samsung,s5pv210-chipid: add S5PV210 ChipID > > So why not call it "chipid"? > "hwinfo" sounds too generic to me; aren't all DT bindings hardware > information? If it is too specific, some other similar drivers won't perfectly match thus they will be placed again under dt-bindings/soc. I was thinking about name "socinfo", but on the other hand why limiting to SoC? I think there are many more devices which provide some kind of read-only hardware information (type, revision, product ID, model etc), therefore - hwinfo. Thanks for the feedback. Best regards, Krzysztof
