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  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 19:19:57 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Paweł Anikiel <pan@...ihalf.com>
Cc:     jarkko.nikula@...ux.intel.com, mika.westerberg@...ux.intel.com,
        robh+dt@...nel.org, p.zabel@...gutronix.de, arnd@...db.de,
        olof@...om.net, soc@...nel.org, dinguyen@...nel.org,
        p.yadav@...com, Tudor.Ambarus@...rochip.com,
        linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
        alexandre.belloni@...tlin.com, sre@...nel.org,
        thunder.leizhen@...wei.com, Jonathan.Cameron@...wei.com,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        ka@...ihalf.com, tn@...ihalf.com, jam@...ihalf.com,
        amstan@...gle.com
Subject: Re: [PATCH v2 1/4] i2c: check bus number property in DesignWare I2C
 Controller

On Tue, Oct 05, 2021 at 04:37:45PM +0200, 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.

Why? This number means nothing, user space has another means to have
this being robust. Sorry, but I don't see any even close to good enough
justification, NAK.

-- 
With Best Regards,
Andy Shevchenko


Powered by blists - more mailing lists