linux-kernel - [PATCH v2 0/2] i2c: Don't assume bus nr 0 if none was specified

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]

Date:	Tue, 27 Mar 2012 11:10:26 +0200
From:	Karol Lewandowski <k.lewandowsk@...sung.com>
To:	w.sang@...gutronix.de
Cc:	ben-linux@...ff.org, m.szyprowski@...sung.com,
	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
	kyungmin.park@...sung.com, hskinnemoen@...il.com,
	bigeasy@...utronix.de, dirk.brandewie@...il.com,
	linux@....linux.org.uk,
	Karol Lewandowski <k.lewandowsk@...sung.com>
Subject: [PATCH v2 0/2] i2c: Don't assume bus nr 0 if none was specified

Changes since v1:
 - Dropped reduntant i2c-octeon change

i2c controller drivers used to assume bus number 0 when none (-1) was
specified.

This worked on non-device tree systems, where one could explicitly
specify bus number via platform data.  On DT-enabled systems bus
number is always -1.

This patchset reworks few remaining drivers to use dynamic bus
allocation when no id has been provided.

[ I've found out this when I've tried to instantiate more than one
  i2c-gpio instance on DT-enabled system. I've, hopefully, fixed few
  other drivers too. ]

Karol Lewandowski (2):
  i2c-pxa: Drop leftover comment
  i2c: Dynamically assign adapter id if it wasn't explictly specified

 drivers/i2c/busses/i2c-gpio.c         |    7 +------
 drivers/i2c/busses/i2c-pca-platform.c |    2 +-
 drivers/i2c/busses/i2c-pxa.c          |    5 -----
 drivers/i2c/busses/i2c-versatile.c    |    9 ++-------
 4 files changed, 4 insertions(+), 19 deletions(-)

-- 
1.7.9.1

--
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/