linux-kernel - [PATCH 0/2] i2c: prevent id collisions in the DT case

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-next>] [day] [month] [year] [list]

Message-Id: <1426177093-26820-1-git-send-email-wsa@the-dreams.de>
Date:	Thu, 12 Mar 2015 17:17:57 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	linux-i2c@...r.kernel.org
Cc:	Wolfram Sang <wsa@...-dreams.de>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Bob Feretich <bob.feretich@...research.com>,
	Jean Delvare <jdelvare@...e.de>, devicetree@...r.kernel.org
Subject: [PATCH 0/2] i2c: prevent id collisions in the DT case

This series tries to fix the issue reported here[1]. In short: A DT entry wants
a fixed id but its probe was deferred. When it was probed again, its id was
taken by a dynamically assigned muxed bus. So, the probe failed.

Let's start all dynamically assigned ids after the highest fixed one. We do
this for legacy platform devices already.

Please let me know what you think. If you can accept the new of-helper
function, I'd like an ack so I can take the patches via my i2c tree.

Thanks,

   Wolfram

[1] http://thread.gmane.org/gmane.linux.drivers.i2c/22166

Wolfram Sang (2):
  of: base: add function to get highest id of an alias stem
  i2c: busses with dynamic ids should start after fixed ids for DT

 drivers/i2c/i2c-core.c |  8 ++++++++
 drivers/of/base.c      | 26 ++++++++++++++++++++++++++
 include/linux/of.h     |  6 ++++++
 3 files changed, 40 insertions(+)

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/