From: Rob Herring <robh@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v4 1/7] dt-bindings: pinctrl: renesas: Add alpha-numerical port support for RZ/V2H
Date: Tue, 17 Dec 2024 05:58:28 -0600 [thread overview]
Message-ID: <20241217115828.GA859895-robh@kernel.org> (raw)
In-Reply-To: <20241216195325.164212-2-biju.das.jz@bp.renesas.com>
On Mon, Dec 16, 2024 at 07:53:11PM +0000, Biju Das wrote:
> RZ/V2H has ports P0-P9 and PA-PB. Add support for defining alpha-numerical
> ports in DT using RZV2H_* macros.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v3->v4:
> * Added new header file with separate RZV2H_P* definitions.
> v3:
> * New patch.
> ---
> .../pinctrl/renesas,r9a09g057-pinctrl.h | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 include/dt-bindings/pinctrl/renesas,r9a09g057-pinctrl.h
>
> diff --git a/include/dt-bindings/pinctrl/renesas,r9a09g057-pinctrl.h b/include/dt-bindings/pinctrl/renesas,r9a09g057-pinctrl.h
> new file mode 100644
> index 000000000000..9008a7e71609
> --- /dev/null
> +++ b/include/dt-bindings/pinctrl/renesas,r9a09g057-pinctrl.h
> @@ -0,0 +1,31 @@
> +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
> +/*
> + * This header provides constants for Renesas RZ/V2H family pinctrl bindings.
> + *
> + * Copyright (C) 2024 Renesas Electronics Corp.
> + *
> + */
> +
> +#ifndef __DT_BINDINGS_RZV2H_PINCTRL_H
> +#define __DT_BINDINGS_RZV2H_PINCTRL_H
> +
> +#include <dt-bindings/pinctrl/rzg2l-pinctrl.h>
> +
> +/* RZV2H_Px = Offset address of PFC_P_mn - 0x20 */
> +#define RZV2H_P0 0
> +#define RZV2H_P1 1
> +#define RZV2H_P2 2
> +#define RZV2H_P3 3
> +#define RZV2H_P4 4
> +#define RZV2H_P5 5
> +#define RZV2H_P6 6
> +#define RZV2H_P7 7
> +#define RZV2H_P8 8
> +#define RZV2H_P9 9
> +#define RZV2H_PA 10
> +#define RZV2H_PB 11
I'm not a fan of defines which are just 'FOO_n n'. And these are if you
speak hex.
> +
> +#define RZV2H_PORT_PINMUX(b, p, f) RZG2L_PORT_PINMUX(RZV2H_P##b, p, f)
> +#define RZV2H_GPIO(port, pin) RZG2L_GPIO(RZV2H_P##port, pin)
So the user does RZV2H_GPIO(A, 123) instead of RZV2H_GPIO(0xA, 123)? Not
sure the bounds checking the port is worth it. pin or function can still
be crap.
Rob
next prev parent reply other threads:[~2024-12-17 11:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 19:53 [PATCH v4 0/7] Add RZ/G3E pinctrl support Biju Das
2024-12-16 19:53 ` [PATCH v4 1/7] dt-bindings: pinctrl: renesas: Add alpha-numerical port support for RZ/V2H Biju Das
2024-12-17 6:31 ` Krzysztof Kozlowski
2024-12-17 7:29 ` Biju Das
2024-12-17 7:50 ` Krzysztof Kozlowski
2024-12-17 8:49 ` Biju Das
2024-12-17 8:59 ` Krzysztof Kozlowski
2024-12-17 9:19 ` Biju Das
2024-12-17 9:44 ` Krzysztof Kozlowski
2024-12-17 9:52 ` Biju Das
2024-12-17 11:58 ` Rob Herring [this message]
2024-12-17 12:33 ` Biju Das
2024-12-18 19:22 ` Rob Herring
2024-12-18 19:24 ` Rob Herring (Arm)
2025-01-03 18:43 ` Geert Uytterhoeven
2025-01-07 11:16 ` Biju Das
2024-12-16 19:53 ` [PATCH v4 2/7] dt-bindings: pinctrl: renesas: Document RZ/G3E SoC Biju Das
2025-01-03 18:45 ` Geert Uytterhoeven
2025-01-07 11:15 ` Biju Das
2024-12-16 19:53 ` [PATCH v4 3/7] pinctrl: renesas: rzg2l: Update r9a09g057_variable_pin_cfg table Biju Das
2025-01-03 18:46 ` Geert Uytterhoeven
2024-12-16 19:53 ` [PATCH v4 4/7] pinctrl: renesas: rzg2l: Add support for RZ/G3E SoC Biju Das
2025-01-03 18:47 ` Geert Uytterhoeven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241217115828.GA859895-robh@kernel.org \
--to=robh@kernel.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox