linux-kernel - Re: [PATCH] i2c: pca954x: Add property to skip disabling PCA954x MUX device

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:   Sun, 29 Sep 2019 14:07:19 +0300
From:   Cengiz Can <cengiz@...nel.wtf>
To:     Biwen Li <biwen.li@....com>
Cc:     linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
        peda@...ntia.se, leoyang.li@....com,
        Wolfram Sang <wsa@...-dreams.de>
Subject: Re: [PATCH] i2c: pca954x: Add property to skip disabling PCA954x
 MUX device

Hello Biwen,

> +       /* Errata ID E-00013 on board LS2088ARDB and LS2088ARDB:
> +        * The point here is that you must not disable a mux if there
> +        * are no pullups on the input or you mess up the I2C. This
> +        * needs to be put into the DTS really as the kernel cannot
> +        * know this otherwise.
> +        */

Can you please explain what a "mess up" is?

And also, should we put this new DTS property in related default
bindings? 

If not, are you planning a documentation update for the users to notify
them about this?

-- 
Cengiz Can <cengiz@...nel.wtf>