mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Eddie James <eajames@linux.ibm.com>, linux-aspeed@lists.ozlabs.org
Cc: joel@jms.id.au, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org,  devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm: dts: aspeed: Blueridge and Rainer: Add VRM presence GPIOs
Date: Mon, 11 Nov 2024 10:15:40 +1030	[thread overview]
Message-ID: <d4196567fc62a24922794b02adad1b6c47750760.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20241108145822.1365072-1-eajames@linux.ibm.com>

On Fri, 2024-11-08 at 08:58 -0600, Eddie James wrote:
> Add GPIO line names to the GPIO expander to describe DCM and
> VRM presence detection lines.
> 
> Signed-off-by: Eddie James <eajames@linux.ibm.com>
> ---
>  arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts | 4 ++--
>  arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier.dts   | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts
> b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts
> index 5f9a46c2abb8..d504ae84db89 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts
> @@ -1232,8 +1232,8 @@ led-controller@60 {
>                 #gpio-cells = <2>;
>  
>                 gpio-line-names =
> -                       "", "", "", "", "", "", "", "",
> -                       "", "", "", "", "", "", "power-config-full-
> load", "";
> +                       "", "", "", "", "", "", "P10_DCM0_PRES",
> "P10_DCM1_PRES",
> +                       "", "", "", "", "PRESENT_VRM_DCM0_N",
> "PRESENT_VRM_DCM1_N", "power-config-full-load", "";
>         };

This ends up generating checkpatch warnings about long lines when I
apply it.

I did a quick, incomplete and random survey of some other devicetrees,
and perhaps exploding out like in [1] might help.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d85b2ad35a2ab

>  
>         led-controller@61 {
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier.dts
> b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier.dts
> index a4aec3010456..eefc69d0d032 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier.dts
> @@ -1280,8 +1280,8 @@ pca_pres3: pca9552@60 {
>                 #gpio-cells = <2>;
>  
>                 gpio-line-names =
> -                       "", "", "", "", "", "", "", "",
> -                       "", "", "", "", "", "", "power-config-full-
> load", "";
> +                       "", "", "", "", "", "", "P10_DCM0_PRES",
> "P10_DCM1_PRES",
> +                       "", "", "", "", "PRESENT_VRM_DCM0_N",
> "PRESENT_VRM_DCM1_N", "power-config-full-load", "";

Similarly here.

Andrew

  reply	other threads:[~2024-11-10 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 14:58 Eddie James
2024-11-10 23:45 ` Andrew Jeffery [this message]
2024-11-12 20:46   ` Eddie James

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=d4196567fc62a24922794b02adad1b6c47750760.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eajames@linux.ibm.com \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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

all inboxes | Powered by JetHome®