From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55759) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2IKC-0006Lb-4w for qemu-devel@nongnu.org; Fri, 27 Nov 2015 07:40:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a2IK8-0006l2-AB for qemu-devel@nongnu.org; Fri, 27 Nov 2015 07:40:28 -0500 Received: from lvps176-28-13-145.dedicated.hosteurope.de ([176.28.13.145]:41549) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a2IK8-0006kd-3J for qemu-devel@nongnu.org; Fri, 27 Nov 2015 07:40:24 -0500 From: Tim Sander Date: Fri, 27 Nov 2015 13:39:52 +0100 Message-ID: <9231947.7qKgf3ndKO@dabox> In-Reply-To: <56582329.5040304@redhat.com> References: <1664220.kcr3K9QWbf@dabox> <56582329.5040304@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [Qemu-devel] [PATCH RFC] i2c-tiny-usb List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, Gerd Hoffmann Hi Paolo Am Freitag, 27. November 2015, 10:32:25 schrieb Paolo Bonzini: > On 26/11/2015 17:35, Tim Sander wrote: > > Below is a patch implementing the i2c-tiny-usb device. > > I am currently not sure about the i2c semantics. I think > > incrementing the address on longer reads is wrong? > > Yes, it is. This is a bus address, not an address inside the device. > > Also you should only call i2c_start_transfer/i2c_end_transfer once. Good to know. I have one more thing, i2cdetect looks like this: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70: 70 71 72 73 74 75 76 77 But i only have a device at 0x50 so most numbers should be "--". I know that i just have to set the read length to zero, to archive that. Currently i don't know how to determine if there is something registered on the requested i2c address? Best regards Tim