linux-kernel - Re: How should I use kernel-defined i2c structs in this driver

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

Message-ID: <85a38a7c-d970-426a-5710-bbdf955cab58@iki.fi>
Date:	Fri, 27 May 2016 03:14:59 +0300
From:	Antti Palosaari <crope@....fi>
To:	Andrey Utkin <andrey_utkin@...tmail.com>,
	kernel-mentors@...enic.com, devel@...verdev.osuosl.org,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-media@...r.kernel.org
Cc:	andrey.utkin@...p.bluecherry.net
Subject: Re: How should I use kernel-defined i2c structs in this driver

On 05/26/2016 04:59 PM, Andrey Utkin wrote:
> Could anybody please give a hint - which kernel-defined i2c objects, and how
> many of them, I need to define and use to substitute these driver-defined
> functions i2c_read(), i2c_write() ?
> https://github.com/bluecherrydvr/linux/blob/release/tw5864/1.16/drivers/media/pci/tw5864/tw5864-config.c
> In a word, there's 4 chips with different addresses, to which this code
> communicates via main chip's dedicated registers.
> Do i need a single i2c_adapter or several?
> Do i need i2c_client entities?
> where should I put what is named "devid" here?
>
> Thanks in advance.

It depends how those are connected at hardware level. Quickly looking I 
think "devid" is here to select proper I2C adapter. So I think there is 
4 I2C adapters and each of those adapter has 1 slave device. Is that 
correct? If yes, then register 4 I2C adapters and register single client 
for each of those adapters.

regards
Antti



-- 
http://palosaari.fi/