1. 24 7月, 2010 1 次提交
    • G
      of: Merge of_platform_bus_type with platform_bus_type · eca39301
      Grant Likely 提交于
      of_platform_bus was being used in the same manner as the platform_bus.
      The only difference being that of_platform_bus devices are generated
      from data in the device tree, and platform_bus devices are usually
      statically allocated in platform code.  Having them separate causes
      the problem of device drivers having to be registered twice if it
      was possible for the same device to appear on either bus.
      
      This patch removes of_platform_bus_type and registers all of_platform
      bus devices and drivers on the platform bus instead.  A previous patch
      made the of_device structure an alias for the platform_device structure,
      and a shim is used to adapt of_platform_drivers to the platform bus.
      
      After all of of_platform_bus drivers are converted to be normal platform
      drivers, the shim code can be removed.
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      Acked-by: NDavid S. Miller <davem@davemloft.net>
      eca39301
  2. 01 4月, 2010 1 次提交
  3. 11 3月, 2010 3 次提交
  4. 08 2月, 2010 1 次提交
  5. 14 12月, 2009 4 次提交
    • M
      microblaze: Support for WB cache · 2ee2ff87
      Michal Simek 提交于
      Microblaze version 7.20.d is the first MB version which can be run
      on MMU linux. Please do not used previous version because they contain
      HW bug.
      Based on WB support was necessary to redesign whole cache design.
      Microblaze versions from 7.20.a don't need to disable IRQ and cache
      before working with them that's why there are special structures for it.
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      2ee2ff87
    • M
      microblaze: Remove panic_timeout init value · 5de23446
      Michal Simek 提交于
      panic_timeout is in BSS section and it is cleared with BSS section.
      This means that value is setup to 0.
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      5de23446
    • M
      microblaze: Lockdep support · bf2d8096
      Michal Simek 提交于
      Microblaze needs to do lock_init very soon because MMU init calls lock functions.
      
      Here is the explanation from Peter Zijlstra why we have to enable
      __ARCH_WANTS_INTERRUPTS_ON_CTSW.
      
      "So we schedule while holding rq->lock (for obvious reasons), but since
      lockdep tracks held locks per tasks, we need to transfer the held state
      from the prev to the next task. We do this by explicity calling
      spin_release(&rq->lock) in context_switch() right before switch_to(),
      and calling spin_acquire(&rq->lock) in
      finish_task_switch()->finish_lock_switch().
      
      Now, for some reason lockdep thinks that interrupts got enabled over the
      context switch (git grep __ARCH_WANTS_INTERRUPTS_ON_CTSW arch/microblaze
      doesn't seem to turn up anything).
      
      Clearly trying to acquire the rq->lock with interrupts enabled is a bad
      idea and lockdep warns you about this."
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      bf2d8096
    • M
      microblaze: GPIO reset support · 42a2478b
      Michal Simek 提交于
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      42a2478b
  6. 21 9月, 2009 1 次提交
  7. 27 7月, 2009 2 次提交
  8. 21 5月, 2009 2 次提交
  9. 27 3月, 2009 1 次提交