[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220705145108.GA2083998-robh@kernel.org>
Date: Tue, 5 Jul 2022 08:51:08 -0600
From: Rob Herring <robh@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Magnus Damm <magnus.damm@...il.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Nishanth Menon <nm@...com>,
Vignesh Raghavendra <vigneshr@...com>,
Tero Kristo <kristo@...nel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] dt-bindings: hwinfo: group devices and add
s5pv210-chipid
On Mon, Jul 04, 2022 at 09:18:31AM +0200, Geert Uytterhoeven wrote:
> Hi Krzysztof,
>
> On Sun, Jul 3, 2022 at 8:35 PM Krzysztof Kozlowski
> <krzysztof.kozlowski@...aro.org> wrote:
> > As suggested by Rob [1], I organized a bit bindings for SoC devices having
> > similar purpose - chip identification.
What's the base? It didn't apply for me.
> >
> > 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?
I'm fine with hwinfo as the color of the shed. I don't think we should
encode where the information comes from.
Rob
Powered by blists - more mailing lists