linux-kernel - Re: [PATCH 00/13] rtc: Add OF device table to I2C drivers that are missing it

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:   Fri, 3 Mar 2017 16:01:34 +0100
From:   Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To:     Javier Martinez Canillas <javier@....samsung.com>
Cc:     linux-kernel@...r.kernel.org, rtc-linux@...glegroups.com,
        Alessandro Zummo <a.zummo@...ertech.it>
Subject: Re: [PATCH 00/13] rtc: Add OF device table to I2C drivers that are
 missing it

Hi,

On 03/03/2017 at 11:29:11 -0300, Javier Martinez Canillas wrote:
> This series add OF device ID tables to RTC I2C drivers whose devices are
> either used in Device Tree source files or are listed in binding docs as
> a compatible string.
> 
> That's done because the plan is to change the I2C core to report proper OF
> modaliases instead of always reporting a MODALIAS=i2c:<foo> regardless if
> a device was registered via DT or using the legacy platform data.
> 

Doesn't that break the DT ABI for all i2c devices? A lot of people are
getting the vendor wrong in the compatible string and because the i2c
core doesn't care, the driver is still probed. Dropping that will break
all those DTBs.
Or will that only affect module autoload?


-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com