1. 29 8月, 2015 1 次提交
  2. 22 8月, 2015 1 次提交
  3. 18 11月, 2014 1 次提交
    • L
      ASoC: Rename snd_soc_dai_driver struct ac97_control field to bus_control · bc263214
      Lars-Peter Clausen 提交于
      Setting the ac97_control field on a CPU DAI tells the ASoC core that this
      DAI in addition to audio data also transports control data to the CODEC.
      This causes the core to suspend the DAI after the CODEC and resume it before
      the CODEC so communication to the CODEC is still possible. This is not
      necessarily something that is specific to AC'97 and can be used by other
      buses with the same requirement. This patch renames the flag from
      ac97_control to bus_control to make this explicit.
      
      While we are at it also change the type from int to bool.
      
      The following semantich patch was used for automatic conversion of the
      drivers:
      // <smpl>
      @@
      identifier drv;
      @@
      struct snd_soc_dai_driver drv = {
      -	.ac97_control
      +	.bus_control
      	=
      -	1
      +	true
      };
      // </smpl>
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      bc263214
  4. 01 11月, 2014 1 次提交
  5. 20 10月, 2014 1 次提交
  6. 17 7月, 2014 1 次提交
  7. 28 5月, 2014 2 次提交
  8. 18 2月, 2014 3 次提交
    • L
      ASoC: adav80x: Split SPI and I2C code into different modules · 0c2d6964
      Lars-Peter Clausen 提交于
      There are a few known (minor) problems with having the support code for both I2C
      and SPI in the same module:
          * We need to be extra careful to make sure to not build the driver into the
            kernel if one of the subsystems is build as a module (Currently only I2C
            can be build as a module).
          * The module init path error handling is rather ugly. E.g. what should be
            done if either the SPI or the I2C driver fails to register. Most drivers
            that implement SPI and I2C in the same module currently fallback to
            undefined behavior in that case. Splitting the the driver into two
            modules, one for each bus, allows the registration of the other bus drive
            to continue without problems if one of them fails.
      
      This patch splits the ADAV80X driver into 3 modules. One core module that
      implements the device logic, but is independent of the bus method used. And one
      module for SPI and I2C each that registers the drivers and sets up the regmap
      struct for the bus.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      0c2d6964
    • L
      ASoC: ssm2602: Split SPI and I2C code into different modules · c924dc68
      Lars-Peter Clausen 提交于
      There are a few known (minor) problems with having the support code for both I2C
      and SPI in the same module:
          * We need to be extra careful to make sure to not build the driver into the
            kernel if one of the subsystems is build as a module (Currently only I2C
            can be build as a module).
          * The module init path error handling is rather ugly. E.g. what should be
            done if either the SPI or the I2C driver fails to register? Most drivers
            that implement SPI and I2C in the same module currently fallback to
            undefined behavior in that case. Splitting the the driver into two
            modules, one for each bus allows the registration of the other bus driver
            to continue without problems if one of them fails.
      
      This patch splits the ssm2602 driver into 3 modules. One core module that
      implements the device logic, but is independent of the bus method used. And one
      module for SPI and I2C each that registers the drivers and sets up the regmap
      struct for the bus.
      
      While we are at it also cleanup the include section of the ssm2602 driver and
      remove unneeded includes.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      c924dc68
    • L
      ASoC: ad193x: Split SPI and I2C code into different modules · 6c3d713e
      Lars-Peter Clausen 提交于
      There are a few known (minor) problems with having the support code for both I2C
      and SPI in the same module:
          * We need to be extra careful to make sure to not build the driver into the
            kernel if one of the subsystems is build as a module (Currently only I2C
            can be build as a module).
          * The module init path error handling is rather ugly. E.g. what should be
            done if either the SPI or the I2C driver fails to register? Most drivers
            that implement SPI and I2C in the same module currently fallback to
            undefined behavior in that case. Splitting the the driver into two
            modules, one for each bus, allows the registration of the other bus driver
            to continue without problems if one of them fails.
      
      This patch splits the AD193X driver into 3 modules. One core module that
      implements the device logic, but is independent of the bus method used. And one
      module for SPI and I2C each that registers the drivers and sets up the regmap
      struct for the bus.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      6c3d713e
  9. 13 2月, 2014 1 次提交
  10. 23 12月, 2013 1 次提交
  11. 14 11月, 2013 1 次提交
  12. 06 11月, 2013 1 次提交
  13. 31 10月, 2013 1 次提交
    • R
      DMA-API: sound: fix dma mask handling in a lot of drivers · c9bd5e69
      Russell King 提交于
      This code sequence is unsafe in modules:
      
      static u64 mask = DMA_BIT_MASK(something);
      ...
      	if (!dev->dma_mask)
      		dev->dma_mask = &mask;
      
      as if a module is reloaded, the mask will be pointing at the original
      module's mask address, and this can lead to oopses.  Moreover, they
      all follow this with:
      
      	if (!dev->coherent_dma_mask)
      		dev->coherent_dma_mask = mask;
      
      where 'mask' is the same value as the statically defined mask, and this
      bypasses the architecture's check on whether the DMA mask is possible.
      
      Fix these issues by using the new dma_coerce_coherent_and_mask()
      function.
      Acked-by: NMark Brown <broonie@linaro.org>
      Acked-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      c9bd5e69
  14. 17 9月, 2013 1 次提交
  15. 30 7月, 2013 3 次提交
  16. 27 6月, 2013 2 次提交
  17. 30 5月, 2013 9 次提交
  18. 15 5月, 2013 1 次提交
  19. 27 3月, 2013 4 次提交
  20. 09 12月, 2012 1 次提交
  21. 18 8月, 2012 1 次提交
  22. 09 8月, 2012 1 次提交
  23. 21 6月, 2012 1 次提交
反馈
建议
客服 返回
顶部