linux-kernel - Re: [PATCH v2 32/60] i2c: mv64xxx: reword according to newest specification

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: <3dwf7ivoybpicavorbfvxinlr5rjef5bgksk3esrknzdl52sea@q2dcnb3ox4f2>
Date: Thu, 11 Jul 2024 10:05:31 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>, 
	linux-i2c@...r.kernel.org, Gregory CLEMENT <gregory.clement@...tlin.com>, 
	linux-kernel@...r.kernel.org, Jean Delvare <jdelvare@...e.com>
Subject: Re: [PATCH v2 32/60] i2c: mv64xxx: reword according to newest
 specification

> > > -	MV64XXX_I2C_STATE_WAITING_FOR_SLAVE_ACK,
> > > -	MV64XXX_I2C_STATE_WAITING_FOR_SLAVE_DATA,
> > > +	MV64XXX_I2C_STATE_WAITING_FOR_TARGET_ACK,
> > > +	MV64XXX_I2C_STATE_WAITING_FOR_TARGET_DATA,
> > 
> > I searched online for the datasheet but couldn't find it. It
> > would be helpful to know if the SLAVE naming comes from the
> > datasheet or if it is arbitrary.
> 
> I was considering datasheet names, but obviously I concluded that these
> are custom names.

Yes, I understand, but sometimes even the action names are
defined in the datasheet, e.g. as a state machine. That's why I
wanted an ack from someone who has the datasheet.

Or, if it's publicly available, I can check it myself, but I
couldn't find it.

Thanks,
Andi