linux-kernel - Re: [patch v5] i2c: mux: mellanox: add driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c530714e-b61e-8a38-a054-9d335f0e8a71@axentia.se>
Date:   Fri, 23 Sep 2016 11:36:10 +0200
From:   Peter Rosin <peda@...ntia.se>
To:     <vadimp@...lanox.com>, <wsa@...-dreams.de>
CC:     <linux-i2c@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <jiri@...nulli.us>, Michael Shych <michaelsh@...lanox.com>
Subject: Re: [patch v5] i2c: mux: mellanox: add driver

On 2016-09-13 22:37, vadimp@...lanox.com wrote:
> From: Vadim Pasternak <vadimp@...lanox.com>
> 
> This driver allows I2C routing controlled through CPLD select registers on
> a wide range of Mellanox systems (CPLD Lattice device).
> MUX selection is provided by digital and analog HW. Analog part is not
> under SW control.
> Digital part is under CPLD control (channel selection/de-selection).
> 
> Connectivity schema.
> i2c-mlxcpld                                 Digital               Analog
> driver
> *--------*                                 * -> mux1 (virt bus2) -> mux ->|
> | I2CLPC | i2c physical                    * -> mux2 (virt bus3) -> mux ->|
> | bridge | bus 1                 *---------*                              |
> | logic  |---------------------> * mux reg *                              |
> | in CPLD|                       *---------*                              |
> *--------*   i2c-mux-mlxpcld          ^    * -> muxn (virt busn) -> mux ->|
>     |        driver                   |                                   |
>     |        *---------------*        |                             Devices
>     |        * CPLD (i2c bus)* select |
>     |        * registers for *--------*
>     |        * mux selection * deselect
>     |        *---------------*
>     |                 |
> <-------->     <----------->
> i2c cntrl      Board cntrl reg
> reg space      space (mux select,
>                IO, LED, WD, info)

Hmm, I'm wondering about the above schematics, which seems a bit
overly complex. I mean, it's not relevant to this driver how the
I2CLPC bridge logic in the CPLD is controlled. Particularly so
since it does not need to be a this particular i2c adapter that
is muxed.

But what I'm really wondering is if this mux can mux same other
bus than is used to control the mux. I.e. is it possible to do
something like this:

  .---.          .-------------.
  |   |          |             |-- i2c2 --
  | l |-- i2c0 --| mlxcpld mux |
  | i |          |             |-- i2c3 --
  | n |          '-------------'
  | u |                 |
  | x |-- i2c1 ---------'
  |   |
  '---'

Or is it always as below, with the mux being controlled from
the same i2c bus it muxes?

  .---.             .-------------.
  | l |             |             |-- i2c1 --
  | i |-- i2c0 --+--| mlxcpld mux |
  | n |          |  |             |-- i2c2 --
  | u |          |  '-------------'
  | x |          |         |
  '---'          '---------'

Cheers,
Peter