linux-kernel - Re: i2c: introduce i2c helper i2c_find_client_by

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]

Message-ID: <20130623124316.GA3025@katana>
Date:	Sun, 23 Jun 2013 14:43:18 +0200
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Bin Gao <bin_gao@...ux.intel.com>
Cc:	Bin Gao <bin.gao@...ux.intel.com>,
	Andy Shevchenko <andy.shevchenko@...il.com>,
	linux-i2c@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: i2c: introduce i2c helper i2c_find_client_by_name()


> >I also wonder about the need to unregister. I have to admit I don't know
> >much about I2C handling in v4l2. But if it requires unregistering from
> >i2c core and registering to v4l2 core, then it sounds to me like we
> >could check if there is a more fundamential cleanup needed? Deferring
> >for now, looks like an issue worth looking at, yet there are other
> >things in the queue first.
> >
> 
> Platform codes are supposed to call i2c_register_board_info() or
> i2c_new_device() to register devices, we don't want to change this.

Exactly.

> Not sure v4l2 can still take over the devices without
> unregistering/registering. Need look deeply into the v4l2 code...

That would help, I currently don't have time for that.

Thanks,

   Wolfram

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)