1. 20 Nov, 2015 1 commit
  2. 05 Nov, 2015 1 commit
  3. 18 Apr, 2015 1 commit
    • Simon Glass's avatar
      cros_ec: exynos: Match up device tree with kernel version · 3fbb7871
      Simon Glass authored
      The U-Boot device trees are slightly different in a few places. Adjust them
      to remove most of the differences. Note that U-Boot does not support the
      concept of interrupts as distinct from GPIOs, so this difference remains.
      For sandbox, use the same keyboard file as for ARM boards and drop the
      host emulation bus which seems redundant.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
  4. 06 Jan, 2015 1 commit
    • Sjoerd Simons's avatar
      cros-ec-keyboard: Synchronize DT binding from linux · 93322749
      Sjoerd Simons authored
      The ChromeOS EC keyboard is used by various different chromebooks. Peach
      pi being the third board in the u-boot tree to use it (snow and peach
      pit the other two). Rather then embedding the same big DT node in the
      peach-pi DT again, copy the dtsi snippit & bindings documentation from
      linux and include it in all 3 boards.
      This slightly changes the dt bindings in u-boot:
        * google,key-rows becomes keypad,num-rows
        * google,key-colums becomes keypad,num-colums
        * google,repeat-delay-ms and google,repeat-rate-ms are no longer used
          and replaced by hardcoded values (similar to tegra kbc)
      Signed-off-by: Sjoerd Simons's avatarSjoerd Simons <sjoerd.simons@collabora.co.uk>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      Tested-by: default avatarSimon Glass <sjg@chromium.org>
  5. 23 Jul, 2014 1 commit
    • Simon Glass's avatar
      stdio: Pass device pointer to stdio methods · 709ea543
      Simon Glass authored
      At present stdio device functions do not get any clue as to which stdio
      device is being acted on. Some implementations go to great lengths to work
      around this, such as defining a whole separate set of functions for each
      possible device.
      For driver model we need to associate a stdio_dev with a device. It doesn't
      seem possible to continue with this work-around approach.
      Instead, add a stdio_dev pointer to each of the stdio member functions.
      Note: The serial drivers have the same problem, but it is not strictly
      necessary to fix that to get driver model running. Also, if we convert
      serial over to driver model the problem will go away.
      Code size increases by 244 bytes for Thumb2 and 428 for PowerPC.
      22: stdio: Pass device pointer to stdio methods
             arm: (for 2/2 boards)  all +244.0  bss -4.0  text +248.0
         powerpc: (for 1/1 boards)  all +428.0  text +428.0
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Acked-by: default avatarMarek Vasut <marex@denx.de>
      Reviewed-by: default avatarMarek Vasut <marex@denx.de>
  6. 18 Mar, 2014 1 commit
  7. 24 Jul, 2013 1 commit
  8. 26 Jun, 2013 1 commit