linux-kernel - Re: [PATCH] i2c: omap: Cleaned up coding style and parameters

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: <Z068zzkafs-xJPt4@darkstar.musicnaut.iki.fi>
Date: Tue, 3 Dec 2024 10:09:51 +0200
From: Aaro Koskinen <aaro.koskinen@....fi>
To: Andreas Kemnade <andreas@...nade.info>
Cc: Dhruv Menon <dhruvmenon1104@...il.com>, vigneshr@...com,
	andi.shyti@...nel.org, jmkrzyszt@...il.com, tony@...mide.com,
	khilman@...libre.com, rogerq@...nel.org, linux-omap@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i2c: omap: Cleaned up coding style and parameters

Hi,

On Tue, Dec 03, 2024 at 08:35:47AM +0100, Andreas Kemnade wrote:
> The sleeps are not shorter, instead possibly longer. I do not think
> that is an issue, AFAIK the idea with sleep range is to bundle wakeups
> and reduce power consumption.

msleep(1) is jiffie-based and can take up to 20 ms. If you replace
it with more precise usleep then polling is more frequent (more
wakeups) 

A.