1. 23 5月, 2017 1 次提交
  2. 28 11月, 2016 1 次提交
    • A
      ARM: davinci: da830-evm: use gpio descriptor for mmc pins · b5e1438c
      Axel Haslam 提交于
      Currently the mmc driver is polling the gpio to know if the
      card was removed.
      
      By using a gpio descriptor instead of the platform callbacks,
      the driver will be able to register the gpio using the mmc core
      APIs designed for this purpose.
      
      This has the advantage that an irq will be registered, and
      polling is no longer needed. Also, a dependency on platform
      callbacks is removed for this board.
      Signed-off-by: NAxel Haslam <ahaslam@baylibre.com>
      [nsekhar@ti.com: minor commit message edit]
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      b5e1438c
  3. 01 11月, 2016 1 次提交
    • D
      ARM: davinci: da8xx: add usb phy clocks · 0004b02a
      David Lechner 提交于
      Up to this point, the USB phy clock configuration was handled manually in
      the board files and in the usb drivers. This adds proper clocks so that
      the usb drivers can use clk_get and clk_enable and not have to worry about
      the details. Also, the related code is removed from the board files and
      replaced with the new clock registration functions.
      
      This also removes the #if IS_ENABLED(CONFIG_USB_MUSB_HDRC) around the musb
      declaration and renames the musb platform device so that we can reference
      it from the usb20 clock even if the musb device is not used.
      Signed-off-by: NDavid Lechner <david@lechnology.com>
      Signed-off-by: NAxel Haslam <ahaslam@baylibre.com>
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      0004b02a
  4. 31 10月, 2016 4 次提交
  5. 02 12月, 2015 1 次提交
  6. 18 11月, 2014 1 次提交
  7. 23 2月, 2014 1 次提交
    • I
      ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif · 67f5185c
      Ivan Khoronzhuk 提交于
      The problem that the set timings code contains the call of Davinci
      platform function davinci_aemif_setup_timing() which is not
      accessible if kernel is built for another platform like Keystone.
      
      The Keysone platform is going to use TI AEMIF driver.
      If TI AEMIF is used we don't need to set timings and bus width.
      It is done by AEMIF driver.
      
      To get rid of davinci-nand driver dependency on aemif platform code
      we moved aemif code to davinci platform.
      
      The platform AEMIF code (aemif.c) has to be removed once Davinci
      will be converted to DT and use ti-aemif.c driver.
      Acked-by: NBrian Norris <computersforpeace@gmail.com>
      Signed-off-by: NIvan Khoronzhuk <ivan.khoronzhuk@ti.com>
      [nsekhar@ti.com: fixed checkpatch error and a build breakage due to
      		 missing include, rebased onto l2-mtd/master]
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      67f5185c
  8. 08 10月, 2013 1 次提交
  9. 30 9月, 2013 1 次提交
  10. 25 9月, 2013 1 次提交
  11. 22 8月, 2013 1 次提交
  12. 03 4月, 2013 1 次提交
  13. 02 4月, 2013 1 次提交
  14. 03 1月, 2013 1 次提交
    • V
      ARM: davinci: da8xx_register_spi() should not register SPI board info · 0273612c
      Vivien Didelot 提交于
      Without this patch, da8xx_register_spi() registers the SPI board info,
      the SPI controller, and sets its number of chipselect to the size of the
      static spi_board_info array. This is bad because a SPI board info may
      declare devices for different SPI buses, and because other code can also
      call spi_register_board_info() (e.g. a daughter board might provide
      additional SPI devices).
      
      This patch removes the spi_register_board_info() call from
      da8xx_register_spi(), renames this last one to da8xx_register_spi_bus()
      to be more explicit, takes the number of chipselect as a function
      parameter, and updates the impacted board-da8{3,5}0-evm.c, and
      board-mityomapl138.c files accordingly. It also sets the SPI platform
      data static, as it doesn't need to be exported.
      Signed-off-by: NVivien Didelot <vivien.didelot@savoirfairelinux.com>
      [nsekhar@ti.com: fixed conflicts with v3.7-rc7, converted to use pr_warn(),
      modified print messages to use __func__]
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      0273612c
  15. 25 12月, 2012 1 次提交
  16. 14 9月, 2012 1 次提交
  17. 05 5月, 2012 1 次提交
  18. 05 1月, 2012 1 次提交
  19. 11 9月, 2011 2 次提交
    • B
      mtd: nand: rename NAND_USE_FLASH_BBT · bb9ebd4e
      Brian Norris 提交于
      Recall the recently added prefix requirements:
       * "NAND_" for flags in nand.h, used in nand_chip.options
       * "NAND_BBT_" for flags in bbm.h, used in nand_chip.bbt_options
              or in nand_bbt_descr.options
      
      Thus, I am changing NAND_USE_FLASH_BBT to NAND_BBT_USE_FLASH.
      
      Again, this flag is found in bbm.h and so should NOT be used in the
      "nand_chip.options" field.
      Signed-off-by: NBrian Norris <computersforpeace@gmail.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      bb9ebd4e
    • B
      mtd: nand: consolidate redundant flash-based BBT flags · a40f7341
      Brian Norris 提交于
      This patch works with the following three flags from two headers (nand.h
      and bbm.h):
        (1) NAND_USE_FLASH_BBT (nand.h)
        (2) NAND_USE_FLASH_BBT_NO_OOB (nand.h)
        (3) NAND_BBT_NO_OOB (bbm.h)
      
      These flags are all related and interdependent, yet they were in
      different headers. Flag (2) is simply the combination of (1) and (3) and
      can be eliminated.
      
      This patch accomplishes the following:
        * eliminate NAND_USE_FLASH_BBT_NO_OOB (i.e., flag (2))
        * move NAND_USE_FLASH_BBT (i.e., flag (1)) to bbm.h
      
      It's important to note that because (1) and (3) are now both found in
      bbm.h, they should NOT be used in the "nand_chip.options" field.
      
      I removed a small section from the mtdnand DocBook because it referes to
      NAND_USE_FLASH_BBT in nand.h, which has been moved to bbm.h.
      Signed-off-by: NBrian Norris <computersforpeace@gmail.com>
      Signed-off-by: NArtem Bityutskiy <Artem.Bityutskiy@nokia.com>
      a40f7341
  20. 22 8月, 2011 1 次提交
  21. 19 7月, 2011 1 次提交
  22. 12 3月, 2011 1 次提交
  23. 20 10月, 2010 1 次提交
    • N
      arm: remove machine_desc.io_pg_offst and .phys_io · 6451d778
      Nicolas Pitre 提交于
      Since we're now using addruart to establish the debug mapping, we can
      remove the io_pg_offst and phys_io members of struct machine_desc.
      
      The various declarations were removed using the following script:
      
        grep -rl MACHINE_START arch/arm | xargs \
        sed -i '/MACHINE_START/,/MACHINE_END/ { /\.\(phys_io\|io_pg_offst\)/d }'
      
      [ Initial patch was from Jeremy Kerr, example script from Russell King ]
      Signed-off-by: NNicolas Pitre <nicolas.pitre@linaro.org>
      Acked-by: Eric Miao <eric.miao at canonical.com>
      6451d778
  24. 24 9月, 2010 4 次提交
  25. 06 8月, 2010 1 次提交
  26. 20 7月, 2010 1 次提交
    • S
      ASoC: davinci: let platform data define edma queue numbers · 48519f0a
      Sekhar Nori 提交于
      Currently the EDMA queue to be used by for servicing ASP through
      internal RAM is fixed to EDMAQ_0 and that to service internal RAM
      from external RAM is fixed to EDMAQ_1.
      
      This may not be the desirable configuration on all platforms. For
      example, on DM365, queue 0 has large fifo size and is more suitable
      for video transfers. Having audio and video transfers on the same
      queue may lead to starvation on audio side.
      
      platform data as defined currently passes a queue number to the driver
      but that remains unused inside the driver.
      
      Fix this by defining one queue each for ASP and RAM transfers in the
      platform data and using it inside the driver.
      
      Since EDMAQ_0 maps to 0, thats the queue that will be used if
      the asp queue number is not initialized. None of the platforms
      currently utilize ping-pong transfers through internal RAM so that
      functionality remains unchanged too.
      
      This patch has been tested on DM644x and OMAP-L138 EVMs.
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      Acked-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      48519f0a
  27. 14 5月, 2010 1 次提交
    • C
      Davinci: aintc/cpintc - use ioremap() · bd808947
      Cyril Chemparathy 提交于
      This patch implements the following:
      
       - interrupt initialization uses ioremap() instead of passing a virtual address
         via davinci_soc_info.
      
       - machine definitions directly point to cp_intc_init() or davinci_irq_init()
      
       - davinci_intc_type and davinci_intc_base now get initialized in controller
         specific init functions instead of davinci_common_init()
      
       - minor fix in davinci_irq_init() to use intc_irq_num instead of
         DAVINCI_N_AINTC_IRQ
      Signed-off-by: NCyril Chemparathy <cyril@ti.com>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      bd808947
  28. 07 5月, 2010 5 次提交
  29. 05 2月, 2010 1 次提交