[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaX2VPAb+vihZ5BEAsGy+jNUdQ8q+3c3Q78uWmqZYeu=g@mail.gmail.com>
Date: Thu, 28 Aug 2025 20:27:22 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Gary Yang <gary.yang@...tech.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, cix-kernel-upstream@...tech.com
Subject: Re: [PATCH 2/3] dt-bindings: pinctrl: Add cix,sky1-pinctrl
On Wed, Aug 27, 2025 at 4:42 AM Gary Yang <gary.yang@...tech.com> wrote:
> Add dt-bindings docs
>
> Signed-off-by: Gary Yang <gary.yang@...tech.com>
I saw Krzysztof reacted to this:
> +++ b/include/dt-bindings/pinctrl/pads-sky1.h
(...)
> +#define CIX_PAD_GPIO001_OFFSET 0x0
> +#define CIX_PAD_GPIO002_OFFSET 0x4
(...)
> +#define CIX_PAD_GPIO001_FUNC_GPIO001 0x0
> +#define CIX_PAD_GPIO002_FUNC_GPIO002 0x0
(...)
> +#define PULL_UP (1 << 6)
> +#define PULL_DOWN (1 << 5)
> +#define ST (1 << 4)
> +#define DS_LEVEL1 0x1
> +#define DS_LEVEL2 0x2
(...)
As stated, this isn't part of bindings so it should not be
include/dt-bindings/pinctrl/*.
If you are using the pinmux = <...>: property, what you can
do however is to put the same defines into
arch/arm64/boot/dts/cix/sky1-pinmux-props.dtsi
and use it the same way.
Then it is not bindings, just some DT data.
Sometimes this distinction isn't clear, and the kernel contain
many offenders to this rule.
Yours,
Linus Walleij
Powered by blists - more mailing lists