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 v2 0/4] pocketbeagle device tree updates
Date: Fri, 18 Aug 2023 11:10:33 -0400 [thread overview]
Message-ID: <20230818151039.40566-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) Remove a dependency cycle.
3) 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.
4) Add a missing mode setting for a GPIO pin.
v2:
- update the patches to remove the pinctrl-0 property early in the set
- patch 2 is new, patches 3 and 4 adjusted accordingly
Trevor Woerner (4):
ARM: dts: am335x-pocketbeagle: update LED information
ARM: dts: am335x-pocketbeagle: remove dependency cycle
ARM: dts: am335x-pocketbeagle: enable pru
ARM: dts: am335x-pocketbeagle: add missing GPIO mux
.../boot/dts/ti/omap/am335x-pocketbeagle.dts | 62 +++++++++++++++----
1 file changed, 49 insertions(+), 13 deletions(-)
--
2.41.0.327.gaa9166bcc0ba
next reply other threads:[~2023-08-18 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 15:10 Trevor Woerner [this message]
2023-08-18 15:10 ` [PATCH v2 1/4] ARM: dts: am335x-pocketbeagle: update LED information Trevor Woerner
2023-08-21 15:36 ` Robert Nelson
2023-08-22 14:37 ` Trevor Woerner
2023-08-18 15:10 ` [PATCH v2 2/4] ARM: dts: am335x-pocketbeagle: remove dependency cycle Trevor Woerner
2023-08-18 15:10 ` [PATCH v2 3/4] ARM: dts: am335x-pocketbeagle: enable pru Trevor Woerner
2023-08-18 15:10 ` [PATCH v2 4/4] ARM: dts: am335x-pocketbeagle: add missing GPIO mux 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=20230818151039.40566-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).