From: "Rafał Miłecki" <zajec5@gmail.com>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
"Rob Herring" <robh@kernel.org>,
"Yicong Yang" <yangyicong@hisilicon.com>,
"Sam Protsenko" <semen.protsenko@linaro.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Jan Dabros" <jsd@semihalf.com>,
"Sven Peter" <sven@svenpeter.dev>,
"Jie Deng" <jie.deng@intel.com>,
"Bence Csókás" <bence98@sch.bme.hu>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH] i2c: brcmstb: allow compiling on BCM4908
Date: Fri, 11 Feb 2022 11:58:06 +0100 [thread overview]
Message-ID: <20220211105806.14341-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
BCM4908 SoCs use the same I2C hardware block as STB and BCM63xx devices.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
drivers/i2c/busses/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 5ea26a7aa1d5..1fbb5f1fa7b1 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -477,8 +477,8 @@ config I2C_BCM_KONA
config I2C_BRCMSTB
tristate "BRCM Settop/DSL I2C controller"
- depends on ARCH_BCM2835 || ARCH_BRCMSTB || BMIPS_GENERIC || \
- ARCH_BCM_63XX || COMPILE_TEST
+ depends on ARCH_BCM2835 || ARCH_BCM4908 || ARCH_BCM_63XX || \
+ ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
default y
help
If you say yes to this option, support will be included for the
--
2.34.1
next reply other threads:[~2022-02-11 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 10:58 Rafał Miłecki [this message]
2022-02-11 17:12 ` [PATCH] i2c: brcmstb: allow compiling on BCM4908 Florian Fainelli
2022-02-11 17:35 ` Wolfram Sang
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=20220211105806.14341-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bence98@sch.bme.hu \
--cc=geert+renesas@glider.be \
--cc=jie.deng@intel.com \
--cc=jsd@semihalf.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-i2c@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=sven@svenpeter.dev \
--cc=wsa@kernel.org \
--cc=yangyicong@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.