Eric Lee / linux-smarc-t335x-v3.2

02 Feb, 2006

6 commits

01 Feb, 2006

10 commits

31 Jan, 2006

1 commit

30 Jan, 2006

1 commit

29 Jan, 2006

1 commit

28 Jan, 2006

1 commit

27 Jan, 2006

3 commits

26 Jan, 2006

2 commits

25 Jan, 2006

4 commits

24 Jan, 2006

1 commit

  • 40727198b   [SUNGEM]: Make PM of PHYs more reliable (#2) ... Browse Code »

    On my latest laptop, I've had occasional PHY dead on wakeup from
    sleep... the PHY would be totally unresponsive even to toggling the hard
    reset line until the machine is powered down... Looking closely at the
    code, I found some possible issues in the way we setup the MDIO lines
    during suspend along with slight divergences from what Darwin does when
    resetting it that may explain the problem. That patch change these and
    the problem appear to be gone for me at least... I also fixed an mdelay
    -> msleep while I was at it to the pmac feature code that is called
    when toggling the PHY reset line since sungem doesn't call it in an
    atomic context anymore.

    Signed-off-by: Benjamin Herrenschmidt b
    Signed-off-by: David S. Miller

    Benjamin Herrenschmidt
     

23 Jan, 2006

1 commit

21 Jan, 2006

1 commit

20 Jan, 2006

7 commits

19 Jan, 2006

1 commit

  • fa1b4f91d   [ARM] safer handling of syscall table padding ... Browse Code »

    ARM entry-common.S needs to know syscall table size; in itself that would
    not be a problem, but there's an additional constraint - some of the
    instructions using it want a constant that would be a multiple of 4.
    So we have to pad syscall table with sys_ni_syscall and that's where
    the trouble begins. .rept pseudo-op wants a constant expression for
    number of repetitions and subtraction of two labels (before and after
    syscall table) doesn't always get simplified to constant early enough
    for .rept. If labels end up in different frags, we lose. And while
    the frag size is large enough (slightly below 4Kb), the syscall table
    is about 1/3 of that. We used to get away with that, but the recent
    changes had been enough to trigger the breakage.

    Proper fix is simple: have a macro (CALL(x)) to populate the table
    instead of using explicit .long x and the first time we include calls.S
    have it defined to .equ NR_syscalls,NR_syscalls+1. Then we can find
    the proper amount of padding on the first inclusion simply by looking
    at NR_syscalls at that time. And that will be constant, no matter what.

    Moreover, the same trick kills the need of having an estimate of padded
    NR_syscalls - it will be calculated for free at the same time.

    Signed-off-by: Al Viro
    Signed-off-by: Russell King

    Al Viro