1. 05 7月, 2011 1 次提交
  2. 09 6月, 2011 1 次提交
  3. 06 6月, 2011 1 次提交
  4. 27 5月, 2011 1 次提交
  5. 20 5月, 2011 1 次提交
  6. 15 3月, 2011 1 次提交
  7. 08 3月, 2011 3 次提交
  8. 23 2月, 2011 3 次提交
  9. 19 1月, 2011 1 次提交
  10. 14 1月, 2011 1 次提交
  11. 13 1月, 2011 1 次提交
  12. 24 12月, 2010 1 次提交
  13. 01 12月, 2010 1 次提交
  14. 18 11月, 2010 1 次提交
  15. 10 11月, 2010 2 次提交
  16. 22 10月, 2010 1 次提交
    • E
      spi: add spi_tegra driver · 0c03a1dd
      Erik Gilling 提交于
      v2 changes:
        from Thierry Reding:
          * add "select TEGRA_SYSTEM_DMA" to Kconfig
        from Grant Likely:
          * add oneline description to header
          * inline references to DRIVER_NAME
          * inline references to BUSY_TIMEOUT
          * open coded bytes_per_word()
          * spi_readl/writel -> spi_tegra_readl/writel
          * move transfer validation to spi_tegra_transfer
          * don't request_mem_region iomem as platform bus does that for us
          * __exit -> __devexit
      
      v3 changes:
        from Russell King:
          * put request_mem_region back int
        from Grant Likely:
          * remove #undef DEBUG
          * add SLINK_ to register bit defines
          * remove unused bytes_per_word
          * make spi_tegra_readl/writel static linine
          * various refactoring for clarity
          * mark err if BSY bit is not cleared after 1000 retries
          * move spinlock to protect setting of RDY bit
          * subsys_initcall -> module_init
      
      v3 changes:
        from Grant Likely:
          * update spi_tegra to use PTR_ERRless dma API
      
      v4 changes:
        from Grant Likely:
          * remove empty spi_tegra_cleanup fucntion
          * allow device ids of -1
      Signed-off-by: NErik Gilling <konkers@android.com>
      Acked-by: NGrant Likely <grant.likely@secretlab.ca>
      Cc: Thierry Reding <thierry.reding@avionic-design.de>
      Cc: Russell King <linux@arm.linux.org.uk>
      
      spi: tegra: cleanups from upstream review
      
      Change-Id: Icecf7e64efcb39de072a15234ba1faa4bad40d25
      Signed-off-by: NErik Gilling <konkers@android.com>
      0c03a1dd
  17. 13 10月, 2010 4 次提交
    • M
      spi/fsl_spi: add eSPI controller support · 8b60d6c2
      Mingkai Hu 提交于
      Add eSPI controller support based on the library code spi_fsl_lib.c.
      
      The eSPI controller is newer controller 85xx/Pxxx devices supported.
      There're some differences comparing to the SPI controller:
      
      1. Has different register map and different bit definition
         So leave the code operated the register to the driver code, not
         the common code.
      
      2. Support 4 dedicated chip selects
         The software can't controll the chip selects directly, The SPCOM[CS]
         field is used to select which chip selects is used, and the
         SPCOM[TRANLEN] field is set to tell the controller how long the CS
         signal need to be asserted. So the driver doesn't need the chipselect
         related function when transfering data, just set corresponding register
         fields to controll the chipseclect.
      
      3. Different Transmit/Receive FIFO access register behavior
         For SPI controller, the Tx/Rx FIFO access register can hold only
         one character regardless of the character length, but for eSPI
         controller, the register can hold 4 or 2 characters according to
         the character lengths. Access the Tx/Rx FIFO access register of the
         eSPI controller will shift out/in 4/2 characters one time. For SPI
         subsystem, the command and data are put into different transfers, so
         we need to combine all the transfers to one transfer in order to pass
         the transfer to eSPI controller.
      
      4. The max transaction length limitation
         The max transaction length one time is limitted by the SPCOM[TRANSLEN]
         field which is 0xFFFF. When used mkfs.ext2 command to create ext2
         filesystem on the flash, the read length will exceed the max value of
         the SPCOM[TRANSLEN] field.
      Signed-off-by: NMingkai Hu <Mingkai.hu@freescale.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      8b60d6c2
    • M
      spi/mpc8xxx: refactor the common code for SPI/eSPI controller · b36ece83
      Mingkai Hu 提交于
      Refactor the common code in file spi_fsl_spi.c to spi_fsl_lib.c used
      by SPI/eSPI controller driver as a library, and leave the QE/CPM SPI
      controller code in the SPI controller driver spi_fsl_spi.c.
      
      Because the register map of the SPI controller and eSPI controller
      is so different, also leave the code operated the register to the
      driver code, not the common code.
      Signed-off-by: NMingkai Hu <Mingkai.hu@freescale.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      b36ece83
    • M
      spi/mpc8xxx: rename spi_mpc8xxx.c to spi_fsl_spi.c · 3272029f
      Mingkai Hu 提交于
      This will pave the way to refactor out the common code which can be used
      by the eSPI controller driver, and rename the SPI controller dirver to the
      file spi_fsl_spi.c.
      Signed-off-by: NMingkai Hu <Mingkai.hu@freescale.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      3272029f
    • G
      spi/topcliff: Tidy up Kconfig help text · cdbc8f04
      Grant Likely 提交于
      The original didn't specify Topcliff in the config prompt text.
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      cdbc8f04
  18. 09 10月, 2010 1 次提交
  19. 01 10月, 2010 3 次提交
  20. 25 5月, 2010 2 次提交
  21. 21 5月, 2010 1 次提交
  22. 16 2月, 2010 2 次提交
  23. 23 1月, 2010 1 次提交
  24. 22 1月, 2010 1 次提交
  25. 21 1月, 2010 3 次提交
  26. 17 12月, 2009 1 次提交
    • J
      spi: Add s3c64xx SPI Controller driver · 230d42d4
      Jassi Brar 提交于
      Each SPI controller has exactly one CS line and as such doesn't
      provide for multi-cs. We implement a workaround to support
      multi-cs by _not_ configuring the mux'ed CS pin for each SPI
      controller. The CS mechanism is assumed to be fully machine
      specific - the driver doesn't even assume some GPIO pin is used
      to control the CS.
      
      The driver selects between DMA and POLLING mode depending upon
      the xfer size - DMA mode for xfers bigger than FIFO size, POLLING
      mode otherwise.
      
      The driver has been designed to be capable of running SoCs since
      s3c64xx and till date, for that reason some of the register fields
      have been passed via, SoC specific, platform data.
      Signed-off-by: NJassi Brar <jassi.brar@samsung.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      230d42d4