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  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]
Date:   Wed, 25 Jan 2017 15:38:29 +0100
From:   Peter Zijlstra <>
To:     Lu Baolu <>
Cc:     Ingo Molnar <>,
        Greg Kroah-Hartman <>,
        Mathias Nyman <>,
        Ingo Molnar <>,,,,, Jiri Slaby <>
Subject: Re: [PATCH v5 1/4] usb: dbc: early driver for xhci debug capability

On Wed, Jan 25, 2017 at 08:27:38PM +0800, Lu Baolu wrote:
> In my driver, udelay() is mostly used to handle time out.
> Xdbc hides most USB things in its firmware. Early printk driver only needs
> to setup the registers/data structures and wait until link ready or time out.
> Without udelay(), I have no means to convert the polling times into waiting
> time.

What is timeout and why? If there is an error other than !ready, I would
expect the hardware to inform you of this through another status bit,

So why can't you poll indefinitely for either ready or error?

Powered by blists - more mailing lists