Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Maud Spierings | GOcontroll <maudspierings@gocontroll.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] arm64: dts: imx8mm: Add pinctrl config definitions
Date: Mon, 24 Feb 2025 09:03:23 +0100	[thread overview]
Message-ID: <b905192e-6cbe-4d84-b31e-f14b47c3a698@kernel.org> (raw)
In-Reply-To: <PA4PR04MB76309B97A0044049F5841C8AC5C02@PA4PR04MB7630.eurprd04.prod.outlook.com>

On 24/02/2025 08:39, Maud Spierings | GOcontroll wrote:
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: Sunday, February 23, 2025 11:27 AM
>  
>> On Tue, Feb 18, 2025 at 09:39:16AM +0100, Maud Spierings wrote:
>>> Currently to configure each IOMUXC_SW_PAD_CTL_PAD the raw value of this
>>> register is written in the dts, these values are not obvious. Add defines
>>> which describe the fields of this register which can be or-ed together to
>>> produce readable settings.
>>>
>>> Signed-off-by: Maud Spierings <maudspierings@gocontroll.com>
>>> ---
>>>   arch/arm64/boot/dts/freescale/imx8mm-pinfunc.h | 27 ++++++++++++++++++++++++++
>>>   1 file changed, 27 insertions(+)
>>>
> 
>> Why are you adding defines which have no users? This is just dead code.
> 
> I will be sending more patches in the near future that will use these bindings, the total stack of patches is starting to grow though so I'm trying to spread it out in multiple easy to manage bits.
> It is also a bit of a test if I can continue using these defines as I plan, or if that will not be accepted and I should instead revert to using raw hex values.

Please wrap your replies.

> 
> If this is a problem then I will keep it in the larger patchset that is to come.

Defines without users is dead code. It's not even easy to validate if
they make any sense without seeing how they are used.

Best regards,
Krzysztof

  reply	other threads:[~2025-02-24  8:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  8:39 [PATCH v2 0/2] arm64: dts: imx8m: Add pinctrl config definitions Maud Spierings via B4 Relay
2025-02-18  8:39 ` [PATCH v2 1/2] arm64: dts: imx8mm: " Maud Spierings via B4 Relay
2025-02-23 10:27   ` Krzysztof Kozlowski
2025-02-24  7:39     ` Maud Spierings | GOcontroll
2025-02-24  8:03       ` Krzysztof Kozlowski [this message]
2025-02-18  8:39 ` [PATCH v2 2/2] arm64: dts: imx8mp: " Maud Spierings via B4 Relay
2025-02-24 13:50 ` [PATCH v2 0/2] arm64: dts: imx8m: " Maud Spierings | GOcontroll

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=b905192e-6cbe-4d84-b31e-f14b47c3a698@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maudspierings@gocontroll.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox