1. 21 9月, 2016 5 次提交
    • M
      ASoC: fsl_ssi: Remove .num_reg_defaults_raw from regmap_config · 7de2763d
      Marek Vasut 提交于
      This driver provides no .reg_defaults_raw in regmap_config, so
      the .num_reg_defaults_raw is useless, and, in fact harmful. It
      triggers kernel crash in regmap_init which tries to access the
      register defaults.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Acked-by: NNicolin Chen <nicoleotsuka@gmail.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      7de2763d
    • M
      ASoC: fsl_ssi: use flat regmap cache · bfcf928d
      Marek Vasut 提交于
      Same as commit ce492b3b
      Subject: drm/fsl-dcu: use flat regmap cache
      
      Using flat regmap cache instead of RB-tree to avoid the following
      lockdep warning on driver load:
      WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:2871 lockdep_trace_alloc+0x104/0x128
      DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
      
      The RB-tree regmap cache needs to allocate new space on first
      writes. However, allocations in an atomic context (e.g. when a
      spinlock is held) are not allowed. The function regmap_write
      calls map->lock, which acquires a spinlock in the fast_io case.
      Since the driver uses MMIO, the regmap bus of type regmap_mmio
      is being used which has fast_io set to true.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Acked-by: NNicolin Chen <nicoleotsuka@gmail.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      bfcf928d
    • M
      ASoC: fsl_spdif: use flat regmap cache · 35ddb157
      Marek Vasut 提交于
      Same as commit ce492b3b
      Subject: drm/fsl-dcu: use flat regmap cache
      
      Using flat regmap cache instead of RB-tree to avoid the following
      lockdep warning on driver load:
      WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:2871 lockdep_trace_alloc+0x104/0x128
      DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
      
      The RB-tree regmap cache needs to allocate new space on first
      writes. However, allocations in an atomic context (e.g. when a
      spinlock is held) are not allowed. The function regmap_write
      calls map->lock, which acquires a spinlock in the fast_io case.
      Since the driver uses MMIO, the regmap bus of type regmap_mmio
      is being used which has fast_io set to true.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Acked-by: NNicolin Chen <nicoleotsuka@gmail.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      35ddb157
    • M
      ASoC: fsl_esai: use flat regmap cache · 0effb865
      Marek Vasut 提交于
      Same as commit ce492b3b
      Subject: drm/fsl-dcu: use flat regmap cache
      
      Using flat regmap cache instead of RB-tree to avoid the following
      lockdep warning on driver load:
      WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:2871 lockdep_trace_alloc+0x104/0x128
      DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
      
      The RB-tree regmap cache needs to allocate new space on first
      writes. However, allocations in an atomic context (e.g. when a
      spinlock is held) are not allowed. The function regmap_write
      calls map->lock, which acquires a spinlock in the fast_io case.
      Since the driver uses MMIO, the regmap bus of type regmap_mmio
      is being used which has fast_io set to true.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Acked-by: NNicolin Chen <nicoleotsuka@gmail.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      0effb865
    • M
      ASoC: fsl_asrc: use flat regmap cache · b4138868
      Marek Vasut 提交于
      Same as commit ce492b3b
      Subject: drm/fsl-dcu: use flat regmap cache
      
      Using flat regmap cache instead of RB-tree to avoid the following
      lockdep warning on driver load:
      WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:2871 lockdep_trace_alloc+0x104/0x128
      DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
      
      The RB-tree regmap cache needs to allocate new space on first
      writes. However, allocations in an atomic context (e.g. when a
      spinlock is held) are not allowed. The function regmap_write
      calls map->lock, which acquires a spinlock in the fast_io case.
      Since the driver uses MMIO, the regmap bus of type regmap_mmio
      is being used which has fast_io set to true.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Acked-by: NNicolin Chen <nicoleotsuka@gmail.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      b4138868
  2. 03 9月, 2016 1 次提交
  3. 19 8月, 2016 3 次提交
  4. 17 8月, 2016 1 次提交
  5. 04 8月, 2016 1 次提交
  6. 03 8月, 2016 2 次提交
  7. 01 8月, 2016 3 次提交
  8. 26 7月, 2016 1 次提交
  9. 25 7月, 2016 2 次提交
  10. 22 7月, 2016 2 次提交
  11. 21 7月, 2016 2 次提交
  12. 18 7月, 2016 2 次提交
  13. 17 7月, 2016 1 次提交
  14. 16 7月, 2016 7 次提交
  15. 15 7月, 2016 7 次提交