linux-kernel - Re: [PATCH v2 0/2] arm64: dts: ti: k3-j7200-som/cpb: Correct i2c bus representations

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]

Date:   Thu, 26 Nov 2020 18:03:57 +0200
From:   Grygorii Strashko <grygorii.strashko@...com>
To:     Peter Ujfalusi <peter.ujfalusi@...com>, <nm@...com>,
        <t-kristo@...com>
CC:     <devicetree@...r.kernel.org>, <nsekhar@...com>,
        <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <vigneshr@...com>
Subject: Re: [PATCH v2 0/2] arm64: dts: ti: k3-j7200-som/cpb: Correct i2c bus
 representations



On 20/11/2020 09:35, Peter Ujfalusi wrote:
> Hi,
> 
> Changes since v1:
> - Added REviewed-by from Vignesh
> - Comment block to explain main_i2c1 connection to CPB
> 
> The main_i2c0 missed the ioexpander present on the SOM itself to control muxes
> to route signals to CPB connectors.
> 
> The main_i2c1 of J7200 is _not_ connected to the i2c1 of CPB, it is connected to
> i2c3, so the devices on the CPB's i2c1 bus are not avalible, but the ones on the
> CPB i2c3 are available under the main_i2c1.
> 
> Add nice line names at the same time to these.
> 
> Regards,
> Peter
> ---
> Peter Ujfalusi (2):
>    arm64: dts: ti: k3-j7200-som-p0: main_i2c0 have an ioexpander on the
>      SOM
>    arm64: dts: ti: k3-j7200-common-proc-board: Correct the name of io
>      expander on main_i2c1
> 
>   .../dts/ti/k3-j7200-common-proc-board.dts     | 23 ++++++++--------
>   arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi   | 26 +++++++++++++++++++
>   2 files changed, 37 insertions(+), 12 deletions(-)
> 

Thank you.
Reviewed-by: Grygorii Strashko <grygorii.strashko@...com>

-- 
Best regards,
grygorii