1. 02 1月, 2014 1 次提交
  2. 12 12月, 2013 1 次提交
  3. 06 12月, 2013 1 次提交
    • T
      net: davinci_emac: Fix platform data handling and make usable for am3517 · dd0df47d
      Tony Lindgren 提交于
      When booted with device tree, we may still have platform data passed
      as auxdata. For am3517 this is needed for passing the interrupt_enable
      and interrupt_disable callbacks that access the omap system control module
      registers. These callback functions will eventually go away when we have
      a separate system control module driver.
      
      Some of the things that are currently passed as platform data we don't need
      to set up as device tree properties as they are always the same on am3517.
      So let's use a new compatible flag for those so we can get those from
      the device tree match data.
      
      Also note that we need to fix setting of phy_dev to NULL instead of an empty
      string as the code later on uses that to find the first phy on the mdio bus.
      This seems to have been caused by 5d69e007 (net: davinci_emac: switch to
      new mdio).
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      dd0df47d
  4. 03 12月, 2013 9 次提交
  5. 27 11月, 2013 1 次提交
    • T
      mmc: omap: Fix I2C dependency and make driver usable with device tree · 9cb238c0
      Tony Lindgren 提交于
      Some features can be configured by the companion I2C chips,
      which may not be available at the probe time. Fix the issue
      by returning -EPROBE_DEFER when the MMC controller slots
      are not configured.
      
      While at it, let's also add minimal device tree support so
      omap24xx platforms can use this driver without legacy mode
      since we claim to support device tree for mach-omap2 based
      systems.
      
      Although adding the minimal device tree support is not strictly
      a fix, it does remove one of the last blockers for dropping a
      bunch of legacy platform data for mach-omap2.
      
      Cc: linux-mmc@vger.kernel.org
      Acked-by: NChris Ball <cjb@laptop.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      9cb238c0
  6. 19 11月, 2013 1 次提交
  7. 18 11月, 2013 5 次提交
  8. 16 11月, 2013 2 次提交
  9. 15 11月, 2013 5 次提交
  10. 13 11月, 2013 4 次提交
  11. 12 11月, 2013 1 次提交
  12. 11 11月, 2013 3 次提交
  13. 07 11月, 2013 2 次提交
    • P
      mtd: nand: omap: combine different flavours of 1-bit hamming ecc schemes · c66d0391
      Pekon Gupta 提交于
      OMAP NAND driver currently supports multiple flavours of 1-bit Hamming
      ecc-scheme, like:
      - OMAP_ECC_HAMMING_CODE_DEFAULT
      	1-bit hamming ecc code using software library
      - OMAP_ECC_HAMMING_CODE_HW
      	1-bit hamming ecc-code using GPMC h/w engine
      - OMAP_ECC_HAMMING_CODE_HW_ROMCODE
      	1-bit hamming ecc-code using GPMC h/w engin with ecc-layout compatible
      	to ROM code.
      
      This patch combines above multiple ecc-schemes into single implementation:
      - OMAP_ECC_HAM1_CODE_HW
      	1-bit hamming ecc-code using GPMC h/w engine with ROM-code compatible
      	ecc-layout.
      Signed-off-by: NPekon Gupta <pekon@ti.com>
      Reviewed-by: NFelipe Balbi <balbi@ti.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Tested-by: NEzequiel Garcia <ezequiel.garcia@free-electrons.com>
      Signed-off-by: NBrian Norris <computersforpeace@gmail.com>
      c66d0391
    • P
      ARM: OMAP2+: cleaned-up DT support of various ECC schemes · ac65caf5
      Pekon Gupta 提交于
      OMAP NAND driver support multiple ECC scheme, which can used in different
      flavours, depending on in-build Hardware engines present on SoC.
      
      This patch updates following in DT bindings related to sectionion of ecc-schemes
      - ti,elm-id: replaces elm_id (maintains backward compatibility)
      - ti,nand-ecc-opts: selection of h/w or s/w implementation of an ecc-scheme
      	depends on ti,elm-id. (supported values ham1, bch4, and bch8)
      - maintain backward compatibility to deprecated DT bindings (sw, hw, hw-romcode)
      
      Below table shows different flavours of ecc-schemes supported by OMAP devices
      +---------------------------------------+---------------+---------------+
      | ECC scheme                            |ECC calculation|Error detection|
      +---------------------------------------+---------------+---------------+
      |OMAP_ECC_HAM1_CODE_HW                  |H/W (GPMC)     |S/W            |
      +---------------------------------------+---------------+---------------+
      |OMAP_ECC_BCH8_CODE_HW_DETECTION_SW     |H/W (GPMC)     |S/W            |
      |(requires CONFIG_MTD_NAND_ECC_BCH)     |               |               |
      +---------------------------------------+---------------+---------------+
      |OMAP_ECC_BCH8_CODE_HW                  |H/W (GPMC)     |H/W (ELM)      |
      |(requires CONFIG_MTD_NAND_OMAP_BCH &&  |               |               |
      | ti,elm-id in DT)                      |               |               |
      +---------------------------------------+---------------+---------------+
      
      To optimize footprint of omap2-nand driver, selection of some ECC schemes
      also require enabling following Kconfigs, in addition to setting appropriate
      DT bindings
      - Kconfig:CONFIG_MTD_NAND_ECC_BCH        error detection done in software
      - Kconfig:CONFIG_MTD_NAND_OMAP_BCH       error detection done by h/w engine
      Signed-off-by: NPekon Gupta <pekon@ti.com>
      Reviewed-by: NFelipe Balbi <balbi@ti.com>
      Acked-by: NTony Lindgren <tony@atomide.com>
      Tested-by: NEzequiel Garcia <ezequiel.garcia@free-electrons.com>
      Signed-off-by: NBrian Norris <computersforpeace@gmail.com>
      ac65caf5
  14. 05 11月, 2013 4 次提交