Devicetree
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Aisheng Dong <aisheng.dong@nxp.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "robh@kernel.org" <robh@kernel.org>,
	"dongas86@gmail.com" <dongas86@gmail.com>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	Frank Li <frank.li@nxp.com>,
	"kernel@dh-electronics.com" <kernel@dh-electronics.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux@ew.tq-group.com" <linux@ew.tq-group.com>
Subject: Re: [PATCH 1/1] arm64: dts: imx8mp: Update pin function file according to Rev.D RM
Date: Mon, 24 Nov 2025 16:19:07 +0100	[thread overview]
Message-ID: <00b6154b-cf95-463d-b46d-2944d2fef8a0@pengutronix.de> (raw)
In-Reply-To: <DU0PR04MB9299811B113C555FD795FDC280D0A@DU0PR04MB9299.eurprd04.prod.outlook.com>

Hello,

On 11/24/25 4:08 PM, Aisheng Dong wrote:
>> From: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> Sent: Monday, November 24, 2025 9:54 PM
>>> Could you help elaborate a bit more why need keep the old defines as I
>>> saw the previous update patch also didn't keep them?
>>
>> Which previous update patch do you refer to?
>>
> 
> I mean this patch:
> 
> commit bcf7206fe9c35e048e1dc90cf62216b0f5eaf091
> Author: Anson Huang <Anson.Huang@nxp.com>
> Date:   Fri Aug 14 17:27:19 2020 +0800
> 
>     arm64: dts: imx8mp: Update pinfunc header file

2020 was the same year the file was added, so any fallout it could have
caused back then would have been minimal anyway.


>> Generally, If the defines are wrong or misleading, I am all for renaming them.
>>
>> In this case, NXP changed their mind and renamed the function in an
>> (unreleased)) reference manual.
> 
> This is not accurate. The RM with updated names has been released.

Thanks for clarifying. I had meant to add a question mark :)

>> The tradeoff here is between:
>>
>> - amount of confusion avoided when we rename USB_OTG to USB
>> - amount of overhead introduced to adapt device trees
>>
>> I think the benefit of the rename is marginal at best and not worth the
>> unnecessary breakage it would impose on countless downstream users with
>> out-of-tree board device trees.
> 
> I agree the benefit of USB renaming may be arguable.
> But how about the remain changes (drop invalid defines and adding new ones)?
> Are they still need to be fixed?

The other changes are ok, although it would be good to add a short info
to the commit message especially about the removed macros if you have
any extra information why these pad functions are no longer applicable.

Thanks,
Ahmad



> 
> Regards
> Aisheng
> 

-- 
Pengutronix e.K.                  |                             |
Steuerwalder Str. 21              | http://www.pengutronix.de/  |
31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |


  reply	other threads:[~2025-11-24 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24  9:54 [PATCH 1/1] arm64: dts: imx8mp: Update pin function file according to Rev.D RM Dong Aisheng
2025-11-24 11:11 ` Alexander Stein
2025-11-24 13:46   ` Aisheng Dong
2025-11-24 13:56     ` Alexander Stein
2025-11-24 12:07 ` Ahmad Fatoum
2025-11-24 13:39   ` Aisheng Dong
2025-11-24 13:54     ` Ahmad Fatoum
2025-11-24 15:08       ` Aisheng Dong
2025-11-24 15:19         ` Ahmad Fatoum [this message]
2025-11-25  0:15         ` Andrew Lunn

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=00b6154b-cf95-463d-b46d-2944d2fef8a0@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=aisheng.dong@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dongas86@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=frank.li@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@dh-electronics.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@ew.tq-group.com \
    --cc=robh@kernel.org \
    --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