linux-kernel - 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 26 May 2016 16:59:54 +0300
From:	Andrey Utkin <andrey_utkin@...tmail.com>
To:	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: How should I use kernel-defined i2c structs in this driver

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.