linux-kernel - Re: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip

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

Message-Id: <201103141700.26457.arnd@arndb.de>
Date:	Mon, 14 Mar 2011 17:00:26 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Waldemar.Rymarkiewicz@...to.com
Cc:	matti.j.aaltonen@...ia.com, linux-i2c@...r.kernel.org,
	linux-kernel@...r.kernel.org, hthebaud@...idefr.com
Subject: Re: [PATCH] NFC: Driver for Inside Secure MicroRead NFC chip

On Monday 14 March 2011, Waldemar.Rymarkiewicz@...to.com wrote:
> >
> >If the usleep_range is trying to synchronize between the NFC 
> >and the I2C chip, you must wait for a notication from the NFC 
> >hardware that it's done.
> 
> No, it's simply there as I have been faceing i2c write error while
> I do two consecutive writes.
> The second fails now and then. That's seems to be a chip issue.
> I will try to investigate this issue.

Ok. It sounds like a bug in the i2c driver, you should also take
a look there. Maybe it has never had to deal with this much
write data at once.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/