On Wed, 2 Nov 2016, Ondrej Zary wrote: > On Wednesday 02 November 2016, Finn Thain wrote: > > On Mon, 31 Oct 2016, Ondrej Zary wrote: > > > > > + NCR5380_write(SELECT_ENABLE_REG, hostdata->id_mask); > > > + NCR5380_write(OUTPUT_DATA_REG, hostdata->id_mask); > > > + NCR5380_write(INITIATOR_COMMAND_REG, ICR_BASE | ICR_ASSERT_DATA | ICR_ASSERT_SEL); > > > + > > > + usleep_range(1000, 20000); > > > > Again, msleep(1) would be more appropriate here. > > WARNING: msleep < 20ms can sleep for up to 20ms; see Documentation/timers/timers-howto.txt > #164: FILE: drivers/scsi/g_NCR5380.c:88: > + msleep(1); > That link is almost 10 years old. I wonder if it is still accurate. Anyway, I take it that you chose usleep_range() so as to make the checkpatch warning go away. Why not use checkpatch.conf for that, or just ignore it? The upper bound for the delay is unimportant and so the warning isn't applicable. Since the lower bound is some unknown number of microseconds, I think msleep(1) nicely expresses the two constraints. Whereas, usleep_range(1000, 20000) misrepresents them. We really don't need three significant figures. If you want precision, surely you would have to measure the time it takes for the IRQ to fire, and derive a worst case (lower bound) from the measurements. -- -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
