1. 16 11月, 2012 1 次提交
  2. 06 11月, 2012 3 次提交
  3. 17 10月, 2012 1 次提交
  4. 13 9月, 2012 1 次提交
  5. 03 7月, 2012 1 次提交
  6. 30 6月, 2012 1 次提交
  7. 27 6月, 2012 1 次提交
  8. 08 5月, 2012 1 次提交
  9. 26 4月, 2012 2 次提交
  10. 05 3月, 2012 2 次提交
    • S
      ARM: dt: Explicitly configure all serial ports on Tegra Cardhu · 8c690fdf
      Stephen Warren 提交于
      The ports are used as follows:
      UART1/A: Routed to debug dongle
      UART2/B: GPS
      UART3/C: Bluetooth
      UART4/D: Routed to debug dongle
      UART5/E: Not connected
      
      The debug dongle has jumpers to connect either UART1/A or UART4/D to
      the DB-9 connector. UART1/A is typically used on Cardhu, and is the option
      we assume here.
      
      For now, only enable UART1/A, and explicitly disable all other ports.
      
      The explicit disable prevents the message "of_serial 70006040.serial:
      no clock-frequency property set" being printed during boot.
      
      Enabling the other ports requires their clocks to be enabled, or accesses
      to the registers will hang. At present, this requires adding entries into
      board-dt-tegra30.c's tegra_dt_clk_init_table[]. Lets punt on that and wait
      for the common clock bindings to set this all up, although that will also
      requiring adding clock support to 8250.c.
      
      While we're at it, fix board-dt-tegra30.c to enable the correct clock for
      the debug UART. We got away with this before, because the bootloader already
      enabled it.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      8c690fdf
    • S
      ARM: tegra: match SoC name not board name in DT board files · c5444f39
      Stephen Warren 提交于
      board-dt-tegra*.c should support any board using Tegra when booted using
      device tree. Instead of explicitly listing all the supported boards,
      which requires a kernel change for each new board, list the supported SoC
      model instead.
      
      Note that the board files do currently have explicit support for setting
      up each board's pinmux. However, it's fairly likely that at least the
      basic devices on any new board will work just fine as set up by the boot-
      loader, and the pinmux data should be moving into device tree soon anyway.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      c5444f39
  11. 07 2月, 2012 1 次提交
  12. 18 12月, 2011 2 次提交