From: Andreas Kemnade <andreas@kemnade.info>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
khilman@baylibre.com, devicetree@vger.kernel.org,
tony@atomide.com, rogerq@kernel.org, aaro.koskinen@iki.fi,
linux-omap@vger.kernel.org
Cc: Andreas Kemnade <andreas@kemnade.info>
Subject: [PATCH 0/4] ARM: dts: omap: omap4-epson-embt2ws: misc gpio definitions
Date: Mon, 30 Sep 2024 23:30:04 +0200 [thread overview]
Message-ID: <20240930213008.159647-1-andreas@kemnade.info> (raw)
Bring the system into a more defined state and do not rely
on things being initialized by bootloader.
Andreas Kemnade (4):
ARM: dts: omap: omap4-epson-embt2ws: define GPIO regulators
ARM: dts: omap: omap4-epson-embt2ws: wire up regulators
ARM: dts: omap: omap4-epson-embt2ws: add unknown gpio outputs
ARM: dts: omap: omap4-epson-embt2ws: add GPIO expander
.../boot/dts/ti/omap/omap4-epson-embt2ws.dts | 175 +++++++++++++++++-
1 file changed, 171 insertions(+), 4 deletions(-)
--
2.39.5
next reply other threads:[~2024-09-30 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 21:30 Andreas Kemnade [this message]
2024-09-30 21:30 ` [PATCH 1/4] ARM: dts: omap: omap4-epson-embt2ws: define GPIO regulators Andreas Kemnade
2024-10-04 7:24 ` Roger Quadros
2024-10-04 7:41 ` Andreas Kemnade
2024-10-04 7:55 ` Roger Quadros
2024-09-30 21:30 ` [PATCH 2/4] ARM: dts: omap: omap4-epson-embt2ws: wire up regulators Andreas Kemnade
2024-10-04 7:25 ` Roger Quadros
2024-10-04 7:38 ` Roger Quadros
2024-10-04 9:01 ` Andreas Kemnade
2024-10-04 9:45 ` Roger Quadros
2024-09-30 21:30 ` [PATCH 3/4] ARM: dts: omap: omap4-epson-embt2ws: add unknown gpio outputs Andreas Kemnade
2024-10-04 7:53 ` Roger Quadros
2024-10-04 11:33 ` Andreas Kemnade
2024-09-30 21:30 ` [PATCH 4/4] ARM: dts: omap: omap4-epson-embt2ws: add GPIO expander Andreas Kemnade
2024-10-02 3:52 ` [PATCH 0/4] ARM: dts: omap: omap4-epson-embt2ws: misc gpio definitions Rob Herring (Arm)
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=20240930213008.159647-1-andreas@kemnade.info \
--to=andreas@kemnade.info \
--cc=aaro.koskinen@iki.fi \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rogerq@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
all inboxes | Powered by JetHome®