Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: David Lechner <david@lechnology.com>
To: "Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>
Cc: Drew Fustini <drew@beagleboard.org>,
	Robert Nelson <robertcnelson@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: am335x-boneblue: add gpio-line-names
Date: Fri, 9 Jul 2021 16:48:19 -0500	[thread overview]
Message-ID: <ee0e8beb-e128-7d6f-de34-f0adabe3c7b9@lechnology.com> (raw)
In-Reply-To: <20210709214230.1581808-1-david@lechnology.com>

On 7/9/21 4:42 PM, David Lechner wrote:
> This adds gpio-line-names to the BeagleBone Blue DTS. The line names
> are based on the BeagleBone Blue rev A2 schematic.
> 
> Signed-off-by: David Lechner <david@lechnology.com>
> ---
>   arch/arm/boot/dts/am335x-boneblue.dts | 143 +++++++++++++++++++++++++-
>   1 file changed, 142 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/am335x-boneblue.dts b/arch/arm/boot/dts/am335x-boneblue.dts
> index 69acaf4ea0f3..90e8b7d63f79 100644
> --- a/arch/arm/boot/dts/am335x-boneblue.dts
> +++ b/arch/arm/boot/dts/am335x-boneblue.dts
> @@ -435,12 +435,153 @@ &dcan1 {
>   	status = "okay";
>   };
>   
> +&gpio0 {
> +	gpio-line-names =
> +		"UART3_CTS", /* M17 */
> +		"UART3_RTS", /* M18 */
> +		"UART2_RX", /* A17 */
> +		"UART2_TX", /* B17 */
> +		"I2C1_SDA", /* B16 */
> +		"I2C1_SCL", /* A16 */
> +		"MMC0_CD", /* C15 */
> +		"SPI1_SS2", /* C18 */
> +		"EQEP_2A", /* V2 */
> +		"EQEP_2B", /* V3 */

Found a typo already. Sending v2 patch...

      reply	other threads:[~2021-07-09 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09 21:42 [PATCH] ARM: dts: am335x-boneblue: add gpio-line-names David Lechner
2021-07-09 21:48 ` David Lechner [this message]

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=ee0e8beb-e128-7d6f-de34-f0adabe3c7b9@lechnology.com \
    --to=david@lechnology.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drew@beagleboard.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robertcnelson@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.com \
    /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