From: Daniel Schultz <d.schultz@phytec.de>
To: <w.egorov@phytec.de>, <trini@konsulko.com>, <u-boot@lists.denx.de>
Cc: <d-gole@ti.com>, <n-francis@ti.com>, <mkorpershoek@baylibre.com>,
<upstream@lists.phytec.de>, Daniel Schultz <d.schultz@phytec.de>
Subject: [PATCH 3/4] configs: phycore_am64x_a53_defconfig: Enable GPIO command
Date: Thu, 16 Jan 2025 03:29:31 -0800 [thread overview]
Message-ID: <20250116112932.1983801-3-d.schultz@phytec.de> (raw)
In-Reply-To: <20250116112932.1983801-1-d.schultz@phytec.de>
Enable the GPIO command to allow access to the GPIO pins.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
---
configs/phycore_am64x_a53_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/phycore_am64x_a53_defconfig b/configs/phycore_am64x_a53_defconfig
index 4b9dcceda45..4a91b72e700 100644
--- a/configs/phycore_am64x_a53_defconfig
+++ b/configs/phycore_am64x_a53_defconfig
@@ -72,6 +72,7 @@ CONFIG_CMD_BOOTEFI_SELFTEST=y
CONFIG_CMD_ASKENV=y
CONFIG_CMD_NVEDIT_EFI=y
CONFIG_CMD_DFU=y
+CONFIG_CMD_GPIO=y
CONFIG_CMD_GPT=y
CONFIG_CMD_I2C=y
CONFIG_CMD_MMC=y
--
2.25.1
next prev parent reply other threads:[~2025-01-16 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 11:29 [PATCH 1/4] board: phytec: common: k3: Add missing boot source to env Daniel Schultz
2025-01-16 11:29 ` [PATCH 2/4] configs: phycore_am64x_a53_defconfig: Fix GPIO controllers Daniel Schultz
2025-01-17 1:42 ` Wadim Egorov
2025-01-16 11:29 ` Daniel Schultz [this message]
2025-01-17 1:42 ` [PATCH 3/4] configs: phycore_am64x_a53_defconfig: Enable GPIO command Wadim Egorov
2025-01-16 11:29 ` [PATCH 4/4] configs: phycore_am64x_a53_defconfig: Fix environment Daniel Schultz
2025-01-17 1:43 ` Wadim Egorov
2025-01-17 1:42 ` [PATCH 1/4] board: phytec: common: k3: Add missing boot source to env Wadim Egorov
2025-01-23 23:14 ` Tom Rini
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=20250116112932.1983801-3-d.schultz@phytec.de \
--to=d.schultz@phytec.de \
--cc=d-gole@ti.com \
--cc=mkorpershoek@baylibre.com \
--cc=n-francis@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.de \
/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