1. 24 10月, 2016 2 次提交
  2. 09 8月, 2016 1 次提交
  3. 08 8月, 2016 1 次提交
  4. 30 5月, 2016 1 次提交
    • S
      ASoC: Introduce SOC_SINGLE_S8_TLV() macro · dcc0799b
      Srinivas Kandagatla 提交于
      This patch introduces SOC_SINGLE_S8_TLV() macro for volume control
      on chips which supports both negative and positive gains with sign
      bit on a 8 bit register, Gain ranges from -128 to +127 with a
      predefined step size.
      Currently we only have support to DOUBLE_S8_TLV() which does not fit
      for cases where we just have separate gain control register for each
      channel.
      
      One of the Qualcomm SOC msm8916 has such gain control register whose gain
      range is from -38.4dB to +38.4dB with step size of 0.3dB.
      Signed-off-by: NSrinivas Kandagatla <srinivas.kandagatla@linaro.org>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      dcc0799b
  5. 21 4月, 2016 2 次提交
  6. 16 2月, 2016 1 次提交
  7. 10 1月, 2016 2 次提交
    • M
      ASoC: Make aux_dev more like a generic component · f2ed6b07
      Mengdong Lin 提交于
      aux_dev is mainly used by the machine driver to specify analog devices,
      which are registered as codecs. Making it more like a generic component
      can help the machine driver to use it to specify any component with
      topology info by name.
      
      Details:
      - Remove the stub 'rtd_aux' array from the soc card.
      - Add a list 'aux_comp_list' to store the components of aux_devs.
        And add a list head 'list_aux' to struct snd_soc_component, for adding
        such components to the above list.
      - Add a 'init' ops to a component for machine specific init.
        soc_bind_aux_dev() will set it to be aux_dev's init. And it will be
        called when probing the component.
      - soc_bind_aux_dev() will also search components by name of an aux_dev,
        since it may not be a codec.
      - Move probing of aux_devs before checking new DAI links brought by
        topology.
      - Move removal of aux_devs later than removal of links. Because topology
        of aux components may register DAIs and the DAI drivers will go with
        removal of the aux components, we want soc_remove_link_dais() to remove
        the DAIs at first.
      Signed-off-by: NMengdong Lin <mengdong.lin@linux.intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      f2ed6b07
    • M
      ASoC: Support registering a DAI dynamically · 68003e6c
      Mengdong Lin 提交于
      Define API snd_soc_register_dai() to add a DAI dynamically and
      create the DAI widgets. Topology can use this API to register DAIs
      when probing a component with topology info. These DAIs's playback
      & capture widgets will be freed when the sound card is unregistered
      and the DAIs will be freed when cleaning up the component.
      
      And a dobj is embedded into the struct snd_soc_dai_driver. Topology
      can use the dobj to find the DAI drivers created by it and free them
      when the topology component is removed.
      Signed-off-by: NMengdong Lin <mengdong.lin@linux.intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      68003e6c
  8. 31 12月, 2015 1 次提交
    • C
      ASoC: Use nested lock for snd_soc_dapm_mutex_lock · 783513ee
      Charles Keepax 提交于
      snd_soc_dapm_mutex_lock currently uses the un-nested call which can
      cause lockdep warnings when called from control handlers (a relatively
      common usage) and using modules. As creating the control causes a
      potential mutex inversion with the handler, creating the control will
      take the controls_rwsem under the dapm_mutex and accessing the control
      will take the dapm_mutex under controls_rwsem.
      
      All the users look like they want to be using the runtime class of the
      lock anyway, so this patch just changes snd_soc_dapm_mutex_lock to use
      the nested call, with the SND_SOC_DAPM_CLASS_RUNTIME class.
      
      Fixes: f6d5e586 ("ASoC: dapm: Add helpers to lock/unlock DAPM mutex")
      Signed-off-by: NCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      783513ee
  9. 13 12月, 2015 1 次提交
  10. 09 12月, 2015 2 次提交
  11. 25 11月, 2015 1 次提交
  12. 19 11月, 2015 1 次提交
    • M
      ASoC: Change the PCM runtime array to a list · 1a497983
      Mengdong Lin 提交于
      Currently the number of DAI links is statically defined by the machine
      driver at build time using an array. This makes it difficult to shrink/
      grow the number of DAI links at runtime in order to reflect any changes
      in topology.
      
      We can change the DAI link array in the core to a list so that PCMs and
      FE DAI links can be added and deleted at runtime to reflect changes in
      use case and DSP topology. The machine driver can still register DAI links
      as an array.
      
      As the 1st step, this patch change the PCM runtime array to a list. A new
      PCM runtime is added to the list when a DAI link is bound successfully.
      
      Later patches will further implement the DAI link list.
      
      More:
      - define snd_soc_new/free_pcm_runtime() to create/free a runtime.
      - define soc_add_pcm_runtime() to add a runtime to the rtd list.
      - define soc_remove_pcm_runtimes() to clean up the runtime list.
      
      - traverse the rtd list to probe the link components and dais.
      
      - Add a field "num" to PCM runtime struct, used to specify the device
        number when creating the pcm device, and for a soc card to access
        its dai_props array.
      
      - The following 3rd party machine/platform drivers iterate the rtd list
        to check the runtimes:
        sound/soc/intel/atom/sst-mfld-platform-pcm.c
        sound/soc/intel/boards/cht_bsw_rt5645.c
        sound/soc/intel/boards/cht_bsw_rt5672.c
        sound/soc/intel/boards/cht_bsw_max98090_ti.c
      Signed-off-by: NMengdong Lin <mengdong.lin@linux.intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      1a497983
  13. 18 11月, 2015 1 次提交
  14. 22 10月, 2015 2 次提交
  15. 16 10月, 2015 1 次提交
    • C
      ASoC: Add info callback for SX_TLV controls · 34198710
      Charles Keepax 提交于
      SX_TLV controls are intended for situations where the register behind
      the control has some non-zero value indicating the minimum gain
      and then gains increasing from there and eventually overflowing through
      zero.
      
      Currently every CODEC implementing these controls specifies the minimum
      as the non-zero value for the minimum and the maximum as the number of
      gain settings available.
      
      This means when the info callback subtracts the minimum value from the
      maximum value to calculate the number of gain levels available it is
      actually under reporting the available levels. This patch fixes this
      issue by adding a new snd_soc_info_volsw_sx callback that does not
      subtract the minimum value.
      
      Fixes: 1d99f243 ("ASoC: core: Rework SOC_DOUBLE_R_SX_TLV add SOC_SINGLE_SX_TLV")
      Signed-off-by: NCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
      Acked-by: NBrian Austin <brian.austin@cirrus.com>
      Tested-by: NBrian Austin <brian.austin@cirrus.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      Cc: stable@vger.kernel.org
      34198710
  16. 01 10月, 2015 1 次提交
  17. 17 9月, 2015 2 次提交
  18. 29 8月, 2015 1 次提交
  19. 24 7月, 2015 1 次提交
  20. 17 7月, 2015 1 次提交
  21. 09 7月, 2015 1 次提交
  22. 07 7月, 2015 1 次提交
  23. 04 6月, 2015 1 次提交
    • L
      ASoC: topology: Add topology core · 8a978234
      Liam Girdwood 提交于
      The topology core parses the FW topology file for known block types and
      instanciates any common ALSA/ASoC objects that it discovers. The core
      also passes any block that is does not understand to client component
      drivers for enumeration.
      
      The core exports some APIs to client drivers in order to load and unload
      firmware topology data as use case require.
      
      Currently the core deals with the following object types :-
      
       o kcontrols. This includes TLV, enumerated and bytes controls.
       o DAPM widgets. All types with any associated kcontrol.
       o DAPM graph.
       o FE PCM. FE PCM capabilities and configuration can be defined.
       o BE DAI Link. BE DAI link capabilities and configuration can be defined.
       o Codec <-> codec style links capabilities and configuration.
      Signed-off-by: NLiam Girdwood <liam.r.girdwood@linux.intel.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      8a978234
  24. 22 5月, 2015 1 次提交
  25. 07 5月, 2015 2 次提交
  26. 28 4月, 2015 3 次提交
  27. 19 4月, 2015 1 次提交
  28. 18 3月, 2015 1 次提交
  29. 16 3月, 2015 1 次提交
  30. 05 3月, 2015 2 次提交
    • L
      ASoC: Remove snd_soc_jack_new() · 77c71765
      Lars-Peter Clausen 提交于
      There are no users of snd_soc_jack_new() left and new users should use
      snd_soc_card_jack_new() instead. So remove the function.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      77c71765
    • L
      ASoC: Allow to register jacks at the card level · 97093996
      Lars-Peter Clausen 提交于
      Jacks are typically card level elements, but are currently registered with a
      CODEC. When it was originally introduced snd_soc_jack_new() took a
      snd_soc_card as its parameter, but at that time DAPM was only implemented at
      the CODEC level and there was only one CODEC per card. This made it clear
      which CODEC to use for the jack DAPM operations. But the multi-component
      patchset added support for having multiple CODECs per card and with it the
      API was updated to register jacks with a specific CODEC instance instead.
      Subsequently DAPM support at the card level has been introduced, but the
      snd_soc_jack_new() API has so remained unchanged.
      
      This leaves us with the issue that the DAPM pins that are managed by the
      jack detection logic usually are part of the card DAPM context but are
      accessed through a CODEC DAPM context. Currently this works fine, but might
      break in the future if we take a more hierarchical approach to DAPM
      contexts.
      
      Furthermore with componentization progressing systems that do not register
      a snd_soc_codec might appear, while these system may still want to able to
      register a jack.
      
      This patch addresses these issues by adding a new function called
      snd_soc_card_jack_new() that can be used to register jacks with the card
      rather than a CODEC.
      
      This new function is mostly identical to snd_soc_jack_new() except that it
      additionally allows to directly specify the DAPM pins associated with the
      jack. This was done since most users of snd_soc_jack_new() typically call
      snd_soc_jack_add_pins() right after it, which is not necessary with the new
      API and allows to reduce the amount of boiler plate code.
      
      The old snd_soc_jack_new() is re-implemented as a wrapper around
      snd_soc_card_jack_new().
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      97093996