[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJH-wD1BbSK=DmBtftpWT7YDbabmvgy1+PPii-8ziHTiQ@mail.gmail.com>
Date: Mon, 29 Apr 2024 08:56:47 -0500
From: Rob Herring <robh@...nel.org>
To: Farouk Bouabid <farouk.bouabid@...obroma-systems.com>
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>, Peter Rosin <peda@...ntia.se>,
Andi Shyti <andi.shyti@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>,
Quentin Schulz <quentin.schulz@...obroma-systems.com>, Heiko Stuebner <heiko@...ech.de>,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH 2/7] dt-bindings: i2c: mux: mule: add dt-bindings for mule
i2c multiplexer
On Fri, Apr 26, 2024 at 11:50 AM Farouk Bouabid
<farouk.bouabid@...obroma-systems.com> wrote:
>
> This patch adds support for the Mule I2C multiplexer.
>
> Mule is an mcu that emulates a set of i2c devices which are reacheable
MCU
reachable
> through an i2c-mux.
>
> The emulated devices share a single i2c address with the mux itself where
> the requested register is what determines which logic is executed (mux or
> device).
Just to be sure, we need a complete binding for the MCU. Is this the
only thing the MCU does?
Rob
Powered by blists - more mailing lists