From: Angelo Dureghello <angelo@kernel-space.org>
To: trini@konsulko.com, hs@denx.de
Cc: u-boot@lists.denx.de, mario.six@gdsys.cc,
Angelo Dureghello <angelo@kernel-space.org>
Subject: [PATCH 2/6] board: stmark2: add i2c0 pinmux pad configuration
Date: Wed, 5 Apr 2023 00:59:24 +0200 [thread overview]
Message-ID: <20230404225928.3032456-2-angelo@kernel-space.org> (raw)
In-Reply-To: <20230404225928.3032456-1-angelo@kernel-space.org>
Add CFG option to enable proper pinmux pad setting for i2c0.
Signed-off-by: Angelo Dureghello <angelo@kernel-space.org>
---
include/configs/stmark2.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/configs/stmark2.h b/include/configs/stmark2.h
index ffc47c8076..af5da096b7 100644
--- a/include/configs/stmark2.h
+++ b/include/configs/stmark2.h
@@ -96,4 +96,6 @@
CFG_SYS_INIT_RAM_SIZE - 12)
+#define CFG_SYS_I2C_0
+
#endif /* __STMARK2_CONFIG_H */
--
2.40.0
next prev parent reply other threads:[~2023-04-04 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 22:59 [PATCH 1/6] m68k: move CONFIG_SYS_I2C to CFG_ namespace Angelo Dureghello
2023-04-04 22:59 ` Angelo Dureghello [this message]
2023-04-11 11:01 ` [PATCH 2/6] board: stmark2: add i2c0 pinmux pad configuration Heiko Schocher
2023-04-04 22:59 ` [PATCH 3/6] m68k: mcf5441x: fix CONFIG_SYS_FSL_I2C definition Angelo Dureghello
2023-04-11 11:02 ` Heiko Schocher
2023-04-04 22:59 ` [PATCH 4/6] i2c: fsl_i2c: fix m68k transferts Angelo Dureghello
2023-04-11 11:02 ` Heiko Schocher
2023-04-04 22:59 ` [PATCH 5/6] m68k: dts: add i2c nodes Angelo Dureghello
2023-04-11 11:03 ` Heiko Schocher
2023-04-04 22:59 ` [PATCH 6/6] m68k: upgrading all boards to dm i2c Angelo Dureghello
2023-04-11 4:41 ` Heiko Schocher
2023-04-11 7:40 ` Angelo Dureghello
2023-04-11 8:00 ` Heiko Schocher
2023-04-11 11:03 ` Heiko Schocher
2023-04-11 11:01 ` [PATCH 1/6] m68k: move CONFIG_SYS_I2C to CFG_ namespace Heiko Schocher
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=20230404225928.3032456-2-angelo@kernel-space.org \
--to=angelo@kernel-space.org \
--cc=hs@denx.de \
--cc=mario.six@gdsys.cc \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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