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?
>
> .../{soc/renesas => hwinfo}/renesas,prr.yaml | 2 +-
> .../samsung,exynos-chipid.yaml} | 2 +-
> .../hwinfo/samsung,s5pv210-chipid.yaml | 30 +++++++++++++++++++
> .../ti,k3-socinfo.yaml} | 2 +-
> MAINTAINERS | 3 ++
> 5 files changed, 36 insertions(+), 3 deletions(-)
> rename Documentation/devicetree/bindings/{soc/renesas => hwinfo}/renesas,prr.yaml (92%)
> rename Documentation/devicetree/bindings/{soc/samsung/exynos-chipid.yaml => hwinfo/samsung,exynos-chipid.yaml} (92%)
> create mode 100644 Documentation/devicetree/bindings/hwinfo/samsung,s5pv210-chipid.yaml
> rename Documentation/devicetree/bindings/{soc/ti/k3-socinfo.yaml => hwinfo/ti,k3-socinfo.yaml} (92%)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
