[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200310100717.GL1987@ninjato>
Date: Tue, 10 Mar 2020 11:07:17 +0100
From: Wolfram Sang <wsa@...-dreams.de>
To: 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>,
Florian Fainelli <f.fainelli@...il.com>,
Rob Herring <robh+dt@...nel.org>, linux-i2c@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 02/89] dt-bindings: i2c: brcmstb: Add BCM2711
BSC/AUTO-I2C binding
On Mon, Feb 24, 2020 at 10:06:04AM +0100, Maxime Ripard wrote:
> The HDMI blocks in the BCM2771 have an i2c controller to retrieve the
> EDID. This block is split into two parts, the BSC and the AUTO_I2C,
> lying in two separate register areas.
>
> The AUTO_I2C block has a mailbox-like interface and will take away the
> BSC control from the CPU if enabled. However, the BSC is the actually
> the same controller than the one supported by the brcmstb driver, and
> the AUTO_I2C doesn't really bring any immediate benefit.
>
> We can model it in the DT as a single device with two register range,
> which will allow us to use or or the other in the driver without
> changing anything in the DT.
>
> Cc: Kamal Dasu <kdasu.kdev@...il.com>
> Cc: Florian Fainelli <f.fainelli@...il.com>
> Cc: Rob Herring <robh+dt@...nel.org>
> Cc: Wolfram Sang <wsa@...-dreams.de>
> Cc: bcm-kernel-feedback-list@...adcom.com
> Cc: linux-i2c@...r.kernel.org
> Cc: devicetree@...r.kernel.org
> Signed-off-by: Maxime Ripard <maxime@...no.tech>
Applied to for-next, thanks!
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists