Skip to content
Snippets Groups Projects
  1. Dec 17, 2013
    • Eric Nelson's avatar
      i.MX6 (DQ/DLS): use macros for mux and pad declarations · b47abc36
      Eric Nelson authored
      
      This allows the use of either or both declarations from
      the files mx6q_pins.h and mx6dl_pins.h.
      
      All board files should include <asm/arch/mx6-pins.h>
      with one of the following defined in boards.cfg
          MX6Q   - for boards targeting i.MX6Q or i.MX6D
          MX6DL  - for boards targeting i.MX6DL
          MX6S   - for boards targeting i.MX6S
          MX6QDL - for boards that support any of the above with
                   run-time detection
      
      Pad declarations will be MX6_PAD_x for single-variant boards
      and MX6Q_PAD_x and MX6DL_PAD_x for boards supporting both
      processor classes.
      
      Signed-off-by: default avatarEric Nelson <eric.nelson@boundarydevices.com>
      Acked-by: default avatarStefano Babic <sbabic@denx.de>
      b47abc36
  2. Nov 13, 2013
  3. Jul 24, 2013
  4. Apr 28, 2013
    • Benoît Thébaudeau's avatar
      imx: iomux-v3: Include PKE and PUE to pad control pull definitions · 7e2173cf
      Benoît Thébaudeau authored
      
      PUE requires PKE to mean something, as do pull values with PUE, so do not
      compell users to explicitly use PKE and PUE everywhere. This is also what is
      done on Linux and what has already been done for i.MX51.
      
      By the way, remove some unused pad control definitions.
      
      There is no change of behavior.
      
      Note that SPI_PAD_CTRL was defined by several boards with a pull value, but
      without PKE or PUE, which means that no pull was actually enabled in the pad.
      This might be a bug in those boards, but this patch does not change the
      behavior, so it just removes the meaningless pull value from those definitions.
      
      Signed-off-by: default avatarBenoît Thébaudeau <benoit.thebaudeau@advansee.com>
      7e2173cf
  5. Apr 22, 2013
Loading