[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bedfe073-6ff4-69ee-fe39-d5802cc3ecfd@gmail.com>
Date: Fri, 24 Apr 2020 10:07:25 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Wolfram Sang <wsa@...-dreams.de>, Maxime Ripard <maxime@...no.tech>
Cc: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
Eric Anholt <eric@...olt.net>, dri-devel@...ts.freedesktop.org,
linux-rpi-kernel@...ts.infradead.org,
bcm-kernel-feedback-list@...adcom.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Dave Stevenson <dave.stevenson@...pberrypi.com>,
Tim Gover <tim.gover@...pberrypi.com>,
Phil Elwell <phil@...pberrypi.com>,
Kamal Dasu <kdasu.kdev@...il.com>, linux-i2c@...r.kernel.org
Subject: Re: [PATCH v2 01/91] i2c: brcmstb: Allow to compile it on BCM2835
On 4/24/2020 9:13 AM, Wolfram Sang wrote:
>
>> config I2C_BRCMSTB
>> tristate "BRCM Settop/DSL I2C controller"
>> - depends on ARCH_BRCMSTB || BMIPS_GENERIC || ARCH_BCM_63XX || \
>> - COMPILE_TEST
>> + depends on ARCH_BCM2835 || ARCH_BRCMSTB || BMIPS_GENERIC || \
>> + ARCH_BCM_63XX || COMPILE_TEST
>
> Isn't there something like ARCH_BROADCOM which we could use here instead
> of adding each and every SoC?
If you are worried about this list growing bigger, I do not think this
is going to happen beyond this changeset (famous last words).
There is no ARCH_BROADCOM because there is typically very little
commonality between SoC architectures within various Broadcom business
units (left hand is not supposed to talk to the right hand) with the
exception of a few peripherals that have been historically shared (NAND,
SPI, XHCI, Ethernet PHYs/switches, etc. etc. This I2C controller
historically came from the STB business unit, which given the market
space has also engineered its own HDMI core and naturally incorporated
the I2C core it already had into the HDMI core. Up until 2711, that HDMI
core was not used by the 283x family at all.
--
Florian
Powered by blists - more mailing lists