All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: drew@beagleboard.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] pocketbeagle device tree updates
Date: Tue, 15 Aug 2023 20:23:03 -0400	[thread overview]
Message-ID: <20230816002308.36800-1-twoerner@gmail.com> (raw)

A couple device-tree updates for pocketbeagle:

1) Update the LED information (the LED on the pocketbeagle is blue, so
   correct the information). Also the "label" property is deprecated so
   replace it with "color" and "function" properties.

2) Now that mainline supports the PRUs via remoteproc, update the pin
   information to enable the PRU pins and set their mode appropriately
   as per the silkscreen.

3) Add a missing mode setting for a GPIO pin.

Trevor Woerner (3):
  ARM: dts: am335x-pocketbeagle: update LED information
  ARM: dts: am335x-pocketbeagle: enable pru
  ARM: dts: am335x-pocketbeagle: add missing GPIO mux

 .../boot/dts/ti/omap/am335x-pocketbeagle.dts  | 59 ++++++++++++++++---
 1 file changed, 50 insertions(+), 9 deletions(-)

-- 
2.41.0.327.gaa9166bcc0ba

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Trevor Woerner <twoerner@gmail.com>
To: drew@beagleboard.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] pocketbeagle device tree updates
Date: Tue, 15 Aug 2023 20:23:03 -0400	[thread overview]
Message-ID: <20230816002308.36800-1-twoerner@gmail.com> (raw)

A couple device-tree updates for pocketbeagle:

1) Update the LED information (the LED on the pocketbeagle is blue, so
   correct the information). Also the "label" property is deprecated so
   replace it with "color" and "function" properties.

2) Now that mainline supports the PRUs via remoteproc, update the pin
   information to enable the PRU pins and set their mode appropriately
   as per the silkscreen.

3) Add a missing mode setting for a GPIO pin.

Trevor Woerner (3):
  ARM: dts: am335x-pocketbeagle: update LED information
  ARM: dts: am335x-pocketbeagle: enable pru
  ARM: dts: am335x-pocketbeagle: add missing GPIO mux

 .../boot/dts/ti/omap/am335x-pocketbeagle.dts  | 59 ++++++++++++++++---
 1 file changed, 50 insertions(+), 9 deletions(-)

-- 
2.41.0.327.gaa9166bcc0ba

             reply	other threads:[~2023-08-16  0:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  0:23 Trevor Woerner [this message]
2023-08-16  0:23 ` [PATCH 0/3] pocketbeagle device tree updates Trevor Woerner
2023-08-16  0:23 ` [PATCH 1/3] ARM: dts: am335x-pocketbeagle: update LED information Trevor Woerner
2023-08-16  0:23   ` Trevor Woerner
2023-08-16  0:23 ` [PATCH 2/3] ARM: dts: am335x-pocketbeagle: enable pru Trevor Woerner
2023-08-16  0:23   ` Trevor Woerner
2023-08-16  0:23 ` [PATCH 3/3] ARM: dts: am335x-pocketbeagle: add missing GPIO mux Trevor Woerner
2023-08-16  0:23   ` Trevor Woerner

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=20230816002308.36800-1-twoerner@gmail.com \
    --to=twoerner@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drew@beagleboard.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.