[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdY-uaQ--vFM+vVPbwa-q9nbSU0rQB+qbL=9m0wVMwA3Aw@mail.gmail.com>
Date: Tue, 8 Nov 2022 13:31:16 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Chester Lin <clin@...e.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
s32@....com, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Larisa Grigore <larisa.grigore@....com>,
Ghennadi Procopciuc <Ghennadi.Procopciuc@....com>,
Andreas Färber <afaerber@...e.de>,
Matthias Brugger <mbrugger@...e.com>
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: add schema for NXP S32 SoCs
Hi Chester,
thanks for your patch!
On Mon, Oct 31, 2022 at 11:09 AM Chester Lin <clin@...e.com> wrote:
> Add DT schema for the pinctrl driver of NXP S32 SoC family.
>
> Signed-off-by: Larisa Grigore <larisa.grigore@....com>
> Signed-off-by: Ghennadi Procopciuc <Ghennadi.Procopciuc@....com>
> Signed-off-by: Chester Lin <clin@...e.com>
(...)
> + nxp,pins:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description:
> + A list of [start, end] pin ID boundaries that correspond to each of
> + the register regions reserved.
That's an interesting approach.
But what about just hardcoding this into the driver instead?
If you have the compatible, surely you know these indexes from
that compatible string?
Yours,
Linus Walleij
Powered by blists - more mailing lists