[lkml]   [2003]   [May]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Test Patch: 2.5.69 Interrupt Latency
    On Fri, 2003-05-16 at 12:48, Paul Fulghum wrote:
    > So always allowing suspend, and selectively doing the
    > wakeup will cause:
    > 1. thrashing for case of one port OC,
    > other port OK with attached device.
    > 2. prevent port with OC from doing resume
    > after clearing OC condition.
    > For the case of all ports hardwired OC, this
    > will work because you suspend the whole controller
    > and never get a valid resume.

    Just to add another argument to disallowing suspend
    instead of qualifying wakeup:

    In 99% of cases, with no OC, this won't come into play.
    In .9% of cases, with transient OC, this won't delay suspend long.
    In .01% of cases, with all hardwired OC ports, suspend does not matter.

    Plus it cures the above problems #1 and #2.

    If problem #1 occurs, I don't see that thrashing is
    any better than not suspending at all.

    Paul Fulghum

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:35    [W:0.023 / U:20.252 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site