From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Renze Nicolai <renze@rnplus.nl>,
linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-aspeed@lists.ozlabs.org, arnd@arndb.de, olof@lixom.net,
soc@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, joel@jms.id.au,
andrew@aj.id.au
Subject: Re: [PATCH v2 1/3] ARM: dts: Modify GPIO table for Asrock X570D4U BMC
Date: Thu, 04 Apr 2024 11:47:38 +1030 [thread overview]
Message-ID: <77829355a18f2afd64343e7e19498473d9263ef6.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240403133037.37782-2-renze@rnplus.nl>
Hi Renze,
In the future, the start of the subject should also include 'aspeed: ',
so:
ARM: dts: aspeed: Modify GPIO table for Asrock X570D4U BMC
On Wed, 2024-04-03 at 15:28 +0200, Renze Nicolai wrote:
> Restructure GPIO table to fit maximum line length.
>
> Fix mistakes found while working on OpenBMC
> userland configuration and based on probing
> the board.
>
> Schematic for this board is not available.
> Because of this the choice was made to
> use a descriptive method for naming the
> GPIOs.
>
> - Push-pull outputs start with output-*
> - Open-drain outputs start with control-*
> - LED outputs start with led-*
> - Inputs start with input-*
> - Button inputs start with button-*
> - Active low signals end with *-n
This seems to be a bit of a mix of following conventions in [1] and
not. It might be helpful to weigh in on that document with your ideas.
[1]: https://github.com/openbmc/docs/blob/master/designs/device-tree-gpio-naming.md
I'll put this series in a tree for Joel for now though, with the
subject fix mentioned above.
I've also re-wrapped the commit messages as it seems you stopped a bit
short of the allowable line length.
Andrew
next prev parent reply other threads:[~2024-04-04 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 13:28 [PATCH v2 0/3] ARM: dts: Update devicetree of Asrock X570D4U BMC Renze Nicolai
2024-04-03 13:28 ` [PATCH v2 1/3] ARM: dts: Modify GPIO table for " Renze Nicolai
2024-04-04 1:17 ` Andrew Jeffery [this message]
2024-04-03 13:28 ` [PATCH v2 2/3] ARM: dts: Disable unused ADC channels " Renze Nicolai
2024-04-03 13:28 ` [PATCH v2 3/3] ARM: dts: Modify I2C bus configuration Renze Nicolai
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=77829355a18f2afd64343e7e19498473d9263ef6.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=renze@rnplus.nl \
--cc=robh+dt@kernel.org \
--cc=soc@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