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  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:   Tue, 5 Oct 2021 18:22:12 +0200
From:   Arnd Bergmann <>
To:     Paweł Anikiel <>
        Andy Shevchenko <>,
        Mika Westerberg <>,
        Rob Herring <>,
        Philipp Zabel <>,
        Arnd Bergmann <>, Olof Johansson <>,
        SoC Team <>, Dinh Nguyen <>,
        Pratyush Yadav <>,
        Tudor Ambarus <>,
        Linux I2C <>,
        Linux Kernel Mailing List <>,
        Alexandre Belloni <>,
        Sebastian Reichel <>,
        "Leizhen (ThunderTown)" <>,
        Jonathan Cameron <>,
        DTML <>,
        Linux ARM <>,, Tomasz Nowicki <>,,
Subject: Re: [PATCH v2 2/4] dt-bindings: add bus number property

On Tue, Oct 5, 2021 at 4:37 PM Paweł Anikiel <> wrote:
> On SoCFPGA systems, it's desireable to have fixed numbering for
> i2c busses, while being able to enable/disable them (e.g. have i2c1
> be mapped to /dev/i2c-1, even though i2c0 is disabled). This can also
> be achieved using devicetree aliases (see i2c_add_adapter). However,
> having the driver be self-contained without relying on aliases is more
> robust.
> Signed-off-by: Paweł Anikiel <>

I don't see how adding a nonstandard property in one of the i2c bus
drivers helps at all. How do you expect this to work when there are
multiple i2c controllers in the system using different drivers? What
should happen if both an alias and the busno property are set?


Powered by blists - more mailing lists