Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 02 2月, 2006 14 次提交
  3. 01 2月, 2006 3 次提交
  5. 31 1月, 2006 1 次提交
  7. 30 1月, 2006 1 次提交
  9. 29 1月, 2006 1 次提交
  11. 28 1月, 2006 1 次提交
  13. 27 1月, 2006 3 次提交
  15. 26 1月, 2006 2 次提交
  17. 25 1月, 2006 4 次提交
  19. 24 1月, 2006 1 次提交
    • B
      [SUNGEM]: Make PM of PHYs more reliable (#2) · 40727198
      由 Benjamin Herrenschmidt 提交于 
      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 <benh@kernel.crashing.org>b
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      40727198
  21. 23 1月, 2006 1 次提交
  23. 21 1月, 2006 1 次提交
  25. 20 1月, 2006 5 次提交
  27. 19 1月, 2006 2 次提交
    • A
      [ARM] safer handling of syscall table padding · fa1b4f91
      由 Al Viro 提交于 
      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: NAl Viro <viro@zeniv.linux.org.uk>
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      fa1b4f91
    • R
      [ARM] Remove CONFIG_BROKEN=y from defconfigs · ea497725
      由 Russell King 提交于 
      Remove CONFIG_BROKEN=y from the ARM defconfigs, and update with
the appropriate changes.  This results in only some unselected
configuration symbols being removed - hence no material effect
on the configuration.
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      ea497725