From: "Bernhard Messerklinger" <bernhard.messerklinger@br-automation.com>
To: u-boot@lists.denx.de
Cc: "Bernhard Messerklinger"
<bernhard.messerklinger@br-automation.com>,
"Tom Rini" <trini@konsulko.com>,
"Wolfgang Wallner" <wolfgang.wallner@br-automation.com>
Subject: [PATCH v4 2/4] board/BuR/common: add parameter for reset controller I2C bus selection
Date: Fri, 4 Apr 2025 09:27:58 +0200 [thread overview]
Message-ID: <20250404072819.69642-3-bernhard.messerklinger@br-automation.com> (raw)
In-Reply-To: <20250404072819.69642-1-bernhard.messerklinger@br-automation.com>
Normally B&R reset controllers are located at I2C bus 0. This patch adds
the possibility to change this bus number with the kconfig option
BR_RESETC_I2CBUS.
Signed-off-by: Bernhard Messerklinger <bernhard.messerklinger@br-automation.com>
---
(no changes since v2)
Changes in v2:
- Move BR_RESETC_I2CBUS to Kconfig
board/BuR/common/Kconfig | 8 ++++++++
board/BuR/common/br_resetc.c | 10 ++++++++--
2 files changed, 16 insertions(+), 2 deletions(-)
create mode 100644 board/BuR/common/Kconfig
diff --git a/board/BuR/common/Kconfig b/board/BuR/common/Kconfig
new file mode 100644
index 00000000000..490201e7407
--- /dev/null
+++ b/board/BuR/common/Kconfig
@@ -0,0 +1,8 @@
+# SPDX-License-Identifier: GPL-2.0+
+#
+# B&R Industrial Automation GmbH - http://www.br-automation.com
+
+config BR_RESETC_I2CBUS
+ int "I2C Bus address of B&R reset controller"
+ depends on SYS_VENDOR = "BuR" && DM_I2C
+ default 0
diff --git a/board/BuR/common/br_resetc.c b/board/BuR/common/br_resetc.c
index f5d09fef3d3..248064f974b 100644
--- a/board/BuR/common/br_resetc.c
+++ b/board/BuR/common/br_resetc.c
@@ -52,10 +52,16 @@ static int resetc_init(void)
{
struct udevice *i2cbus;
int rc;
+#if !defined(BR_RESETC_I2CBUS)
+ int busno = 0;
+#else
+ int busno = CONFIG_BR_RESETC_I2CBUS;
+#endif
+
+ rc = uclass_get_device_by_seq(UCLASS_I2C, busno, &i2cbus);
- rc = uclass_get_device_by_seq(UCLASS_I2C, 0, &i2cbus);
if (rc) {
- printf("Cannot find I2C bus #0!\n");
+ printf("Cannot find I2C bus #%d!\n", busno);
return -1;
}
--
2.49.0
next prev parent reply other threads:[~2025-04-05 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 7:27 [PATCH v4 0/4] Add support for BR Xilinx Zynq boards in mainline U-Boot Bernhard Messerklinger
2025-04-04 7:27 ` [PATCH v4 1/4] board/BuR/common: use strlcpy instead of strncpy Bernhard Messerklinger
2025-04-04 7:27 ` Bernhard Messerklinger [this message]
2025-04-04 7:27 ` [PATCH v4 3/4] board/BuR/common: split br_resetc_bmode function Bernhard Messerklinger
2025-04-04 7:28 ` [PATCH v4 4/4] board/BuR/zynq: initial commit Bernhard Messerklinger
2025-04-14 6:48 ` Michal Simek
2025-04-17 10:11 ` [PATCH v4 0/4] Add support for BR Xilinx Zynq boards in mainline U-Boot Michal Simek
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=20250404072819.69642-3-bernhard.messerklinger@br-automation.com \
--to=bernhard.messerklinger@br-automation.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wolfgang.wallner@br-automation.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