From: Thomas Gleixner <tglx@linutronix.de>
To: Andre Przywara <andre.przywara@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 06/15] irqchip/sunxi-nmi: Support Allwinner A523 NMI controller
Date: Wed, 05 Mar 2025 08:41:28 +0100 [thread overview]
Message-ID: <87frjr6i1j.ffs@tglx> (raw)
In-Reply-To: <20250304222309.29385-7-andre.przywara@arm.com>
On Tue, Mar 04 2025 at 22:23, Andre Przywara wrote:
>
> -struct sunxi_sc_nmi_reg_offs {
> +struct sunxi_sc_nmi_data {
> u32 ctrl;
> u32 pend;
> u32 enable;
> + u32 enable_val;
The data structure name and the corresponding variable/argument name
were making the code pretty obvious, but now this is opaque and
incomprehensible.
data::ctrl does not even give the slightest hint what this is about. You
need to read up in the code to figure out what it means. Something like:
struct sunxi_sc_nmi_data {
u32 reg_offs_ctrl;
u32 reg_offs_pend;
u32 reg_offs_enable;
u32 enable_val;
};
or even better:
struct sunxi_sc_nmi_data {
struct {
u32 ctrl;
u32 pend;
u32 enable;
} reg_offs;
u32 enable_val;
};
makes it clear and obvious, no?
> +static const struct sunxi_sc_nmi_data sun55i_a523_data __initconst = {
> + .ctrl = SUN9I_NMI_CTRL,
> + .pend = SUN9I_NMI_PENDING,
> + .enable = SUN9I_NMI_ENABLE,
> + .enable_val = BIT(31),
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#struct-declarations-and-initializers
Thanks,
tglx
next prev parent reply other threads:[~2025-03-05 7:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 22:22 [PATCH v2 00/15] arm64: dts: allwinner: Add basic Allwinner A523 support Andre Przywara
2025-03-04 22:22 ` Andre Przywara
2025-03-04 22:22 ` [PATCH v2 01/15] dt-bindings: mmc: sunxi: Simplify compatible string listing Andre Przywara
2025-03-04 22:22 ` [PATCH v2 02/15] dt-bindings: mmc: sunxi: add compatible strings for Allwinner A523 Andre Przywara
2025-03-04 22:22 ` [PATCH v2 03/15] dt-bindings: watchdog: sunxi: add Allwinner A523 compatible string Andre Przywara
2025-03-04 22:22 ` [PATCH v2 04/15] watchdog: sunxi_wdt: Add support for Allwinner A523 Andre Przywara
2025-03-04 22:22 ` [PATCH v2 05/15] dt-bindings: irq: sun7i-nmi: document the Allwinner A523 NMI controller Andre Przywara
2025-03-05 16:45 ` Rob Herring (Arm)
2025-03-04 22:23 ` [PATCH v2 06/15] irqchip/sunxi-nmi: Support " Andre Przywara
2025-03-05 7:41 ` Thomas Gleixner [this message]
2025-03-05 11:55 ` Andre Przywara
2025-03-04 22:23 ` [PATCH v2 07/15] dt-bindings: phy: document Allwinner A523 USB-2.0 PHY Andre Przywara
2025-03-04 22:23 ` Andre Przywara
2025-03-04 22:23 ` [PATCH v2 08/15] arm64: dts: allwinner: Add Allwinner A523 .dtsi file Andre Przywara
2025-03-05 18:46 ` Jernej Škrabec
2025-03-07 0:55 ` Andre Przywara
2025-03-04 22:23 ` [PATCH v2 09/15] dt-bindings: vendor-prefixes: Add YuzukiHD name Andre Przywara
2025-03-04 22:23 ` [PATCH v2 10/15] dt-bindings: arm: sunxi: Add new board names for A523 generation Andre Przywara
2025-03-05 7:41 ` Krzysztof Kozlowski
2025-03-04 22:23 ` [PATCH v2 11/15] arm64: dts: allwinner: a523: add Avaota-A1 router support Andre Przywara
2025-03-05 18:48 ` Jernej Škrabec
2025-03-04 22:23 ` [PATCH v2 12/15] arm64: dts: allwinner: a523: add X96Q-Pro+ support Andre Przywara
2025-03-05 18:50 ` Jernej Škrabec
2025-03-04 22:23 ` [PATCH v2 13/15] arm64: dts: allwinner: a523: add Radxa A5E support Andre Przywara
2025-03-05 18:52 ` Jernej Škrabec
2025-03-04 22:23 ` [PATCH v2 14/15] dt-bindings: arm: sunxi: Add YuzukiHD Chameleon board name Andre Przywara
2025-03-04 22:23 ` [PATCH v2 15/15] arm64: dts: allwinner: h616: add YuzukiHD Chameleon support Andre Przywara
2025-03-05 18:54 ` Jernej Škrabec
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=87frjr6i1j.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.