Skip to content
Snippets Groups Projects
  1. Jun 02, 2014
    • Fugang Duan's avatar
      i2c: imx: update i2c clock divider for each transaction · 9b2a6da3
      Fugang Duan authored
      
      Since IMX serial SOCs support low bus freq mode, some clocks freq
      may change to save power. I2C needs to check the clock source and
      update the divider.
      
      For example:
      i.MX6SL I2C clk is from IPG_PERCLK which is sourced from IPG_CLK.
      Under normal operation, IPG_CLK is 66MHz, ipg_perclk is at 22MHz.
      In low bus freq mode, IPG_CLK is at 12MHz and IPG_PERCLK is down
      to 4MHz. So the I2C driver must update the divider register for
      each transaction when the current IPG_PERCLK is not equal to the
      clock of previous transaction.
      
      Signed-off-by: default avatarFugang Duan <B38611@freescale.com>
      [wsa: removed an outdated comment and simplified debug output]
      Signed-off-by: default avatarWolfram Sang <wsa@the-dreams.de>
      9b2a6da3
    • Fugang Duan's avatar
      i2c: imx: fix the i2c bus hang issue when do repeat restart · 054b62d9
      Fugang Duan authored
      Test i2c device Maxim max44009, datasheet is located at:
      http://www.maximintegrated.com/datasheet/index.mvp/id/7175
      
      
      
      The max44009 support repeat operation like:
      read -> repeat restart -> read/write
      
      The current i2c imx host controller driver don't support this
      operation that causes i2c bus hang due to "MTX" is cleared in
      .i2c_imx_read(). If "read" is the last message there have no problem,
      so the current driver supports all SMbus operation like:
      write -> repeat restart -> read/write
      
      IMX i2c controller for master receiver has some limitation:
      - If it is the last byte for one operation, it must generate STOP
        signal before read I2DR to prevent controller from generating another
        clock cycle.
      - If it is the last byte in the read, and then do repeat restart, it must
        set "MTX" before read I2DR to prevent controller from generating another
        extra clock cycle.
      
      The patch is to fix the issue.
      
      Signed-off-by: default avatarFugang Duan <B38611@freescale.com>
      Signed-off-by: default avatarWolfram Sang <wsa@the-dreams.de>
      054b62d9
  2. May 22, 2014
  3. Jan 03, 2014
  4. Dec 12, 2013
  5. Oct 10, 2013
  6. Aug 23, 2013
    • Wolfram Sang's avatar
      i2c: move OF helpers into the core · 687b81d0
      Wolfram Sang authored
      
      I2C of helpers used to live in of_i2c.c but experience (from SPI) shows
      that it is much cleaner to have this in the core. This also removes a
      circular dependency between the helpers and the core, and so we can
      finally register child nodes in the core instead of doing this manually
      in each driver. So, fix the drivers and documentation, too.
      
      Signed-off-by: default avatarWolfram Sang <wsa@the-dreams.de>
      687b81d0
  7. Aug 19, 2013
  8. Aug 15, 2013
  9. Jun 25, 2013
  10. Jun 12, 2013
  11. Feb 21, 2013
  12. Jan 24, 2013
  13. Oct 15, 2012
    • Shawn Guo's avatar
      i2c: imx: remove cpu_is_xxx by using platform_device_id · 5bdfba29
      Shawn Guo authored
      
      This is some amount of work left/forgot from device tree conversion.
      Instead of checking cpu_is_xxx to determine the controller type, the
      driver should use platform_device_id, which should match the device
      tree compatible string.
      
      The patch changes the driver to use platform_device_id rather than
      cpu_is_xxx to determine the controller type/version.  It also updates
      the platform code and device tree source accordingly.
      
      As the result, mach/hardware.h inclusion gets removed from the driver.
      
      Signed-off-by: default avatarShawn Guo <shawn.guo@linaro.org>
      Acked-by: default avatarSascha Hauer <s.hauer@pengutronix.de>
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
      Cc: Wolfram Sang <w.sang@pengutronix.de>
      Cc: linux-i2c@vger.kernel.org
      5bdfba29
  14. Sep 14, 2012
  15. Sep 11, 2012
  16. Jul 10, 2012
  17. Jul 09, 2012
  18. Jul 08, 2012
  19. Jul 01, 2012
  20. May 12, 2012
  21. Feb 29, 2012
  22. Feb 01, 2012
  23. Sep 14, 2011
  24. Oct 18, 2010
    • Marc Kleine-Budde's avatar
      i2c-imx: do not allow interruptions when waiting for I2C to complete · e39428d5
      Marc Kleine-Budde authored
      
      The i2c_imx_trx_complete() function is using
      wait_event_interruptible_timeout() to wait for the I2C controller to
      signal that it has completed an I2C bus operation. If the process that
      causes the I2C operation receives a signal, the wait will be
      interrupted, returning an error. It is better to let the I2C operation
      finished before handling the signal (i.e. returning into userspace).
      
      It is safe to use wait_event_timeout() instead, because the timeout
      will allow the process to exit if the I2C bus hangs. It's also better
      to allow the I2C operation to finish, because unacknowledged I2C
      operations can cause the I2C bus to hang.
      
      Signed-off-by: default avatarMarc Kleine-Budde <mkl@pengutronix.de>
      Reviewed-by: default avatarWolfram Sang <w.sang@pengutronix.de>
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      e39428d5
  25. Apr 20, 2010
    • Arnaud Patard's avatar
      i2c-imx: fix error handling · da9c99fc
      Arnaud Patard authored
      
      - Return -ETIMEDOUT on bus busy error
      - Fix timeout test "time_after(jiffies, orig_jiffies + HZ / 1000)" :
        By default, HZ=100 on arm. This means that this test has no chances to
        work and may result in a dead loop. Set timeout to 500ms.
      - Don't try to send a new message if we failed to transmit
        previous one. This was preventing to recover from error on my system
      
      Signed-off-by: default avatarArnaud Patard <apatard@mandriva.com>
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      da9c99fc
  26. Mar 30, 2010
    • Tejun Heo's avatar
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo authored
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Guess-its-ok-by: default avatarChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  27. Mar 07, 2010
  28. Jan 24, 2010
Loading