1. 01 5月, 2014 1 次提交
  2. 01 4月, 2014 1 次提交
  3. 28 3月, 2014 1 次提交
  4. 27 3月, 2014 2 次提交
  5. 19 3月, 2014 2 次提交
  6. 18 3月, 2014 2 次提交
  7. 14 3月, 2014 1 次提交
  8. 11 3月, 2014 1 次提交
  9. 06 3月, 2014 1 次提交
    • N
      regmap: add regmap_parse_val api · 13ff50c8
      Nenghua Cao 提交于
          In some cases, we need regmap's format parse_val function
      to do be/le translation according to the bus configuration.
      For example, snd_soc_bytes_put() uses regmap to write/read values,
      and use cpu_to_be() directly to covert MASK into big endian. This
      is a defect, and should use regmap's format function to do it according
      to bus configuration.
      Signed-off-by: NNenghua Cao <nhcao@marvell.com>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      13ff50c8
  10. 26 2月, 2014 3 次提交
  11. 22 2月, 2014 2 次提交
  12. 20 2月, 2014 1 次提交
  13. 16 2月, 2014 2 次提交
  14. 15 2月, 2014 1 次提交
  15. 12 2月, 2014 1 次提交
  16. 03 2月, 2014 2 次提交
  17. 28 1月, 2014 1 次提交
    • D
      regmap: cache: Handle stride > 1 in sync_block_raw_flush · 78ba73ee
      Dylan Reid 提交于
      regcache_sync_block_raw_flush takes the address of the base register
      and the address of one past the last register to write to.  "count" is
      the number of registers in the range, not the number of bytes, it
      should be (end addr - start addr) / stride. Without accounting for
      strides greater than one, registers past the end might be synced or
      the writeable_reg callback at the beginning of _regmap_raw_write will
      fail and nothing will be written.
      Signed-off-by: NDylan Reid <dgreid@chromium.org>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      78ba73ee
  18. 30 12月, 2013 1 次提交
  19. 17 12月, 2013 2 次提交
  20. 26 11月, 2013 1 次提交
  21. 24 11月, 2013 1 次提交
  22. 21 11月, 2013 1 次提交
  23. 12 11月, 2013 1 次提交
  24. 29 10月, 2013 1 次提交
  25. 24 10月, 2013 1 次提交
  26. 22 10月, 2013 1 次提交
    • Y
      regmap: irq: clear status when disable irq · 4bd7145b
      Yi Zhang 提交于
      clear the status bit if the mask register doesn't prevent
      the chip level irq from being asserted
      
      OR in the following sequence, there will be irq storm happens:
      1) interrupt is triggered;
      2) another thread disables it(the mask bit is set);
      3) _Then_ the interrupt thread is not ACKed(the status bit is not cleared),
         and it's ignored;
      4) if the irq is still asserted because of the uncleared status bit,
         the irq storm happens;
      Signed-off-by: NYi Zhang <yizhang@marvell.com>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      4bd7145b
  27. 15 10月, 2013 2 次提交
  28. 14 10月, 2013 1 次提交
  29. 11 10月, 2013 2 次提交