03 Apr, 2014

1 commit


31 Mar, 2014

1 commit


25 Mar, 2014

1 commit


24 Mar, 2014

1 commit


23 Mar, 2014

1 commit


19 Mar, 2014

1 commit


14 Mar, 2014

1 commit

  • …e/sound into for-next

    ASoC: Updates for v3.15

    This is mostly a few additional fixes from Lars-Peter, a new driver and
    cleaning up a git failure with merging the Intel branch (combined with
    an xargs failure to pay attention to error codes). The history lists a
    bunch of additional commits for the branch but the content of those
    commits is actually present already but not recorded in history due to
    git failing. Unfortunately xargs is used in the merge script and it
    doesn't do a good job of noticing errors from the commands it invokes.

    Takashi Iwai
     

13 Mar, 2014

8 commits


11 Mar, 2014

3 commits


10 Mar, 2014

2 commits


06 Mar, 2014

7 commits


05 Mar, 2014

3 commits

  • R-Car sound has SCU unit which has SRC/CTU/MIX/DVC,
    and current rsnd driver has scu.c and scu module.
    Current scu.c has SRC support only.
    My first concept was control these feature on scu.c
    but, it become difficult and un-understandable now.
    This patch rename scu to src

    Signed-off-by: Kuninori Morimoto
    Signed-off-by: Mark Brown

    Kuninori Morimoto
     
  • Current rsnd driver is assuming that SCU/SRU ID is
    same as SSIU/SSI ID, because Gen1 can't select it.
    But, Gen2 can select it.
    The SCU/SRU/SSIU/SSI pair depends on the platform.
    This patch get correct SCU ID from platform info.
    To keep compatible, it still assuming SCU ID = SSI ID
    if platform doesn't have info

    Signed-off-by: Kuninori Morimoto
    Signed-off-by: Mark Brown

    Kuninori Morimoto
     
  • R-Car sound DAI consists from SSI/SCU/SSIU/SRU...
    Current R-Car sound DAI is decided from these settings,
    but it is intuitively unclear, and is not good design for DT support.
    This patch adds new rsnd_dai_platform_info to solve this issue.

    But now, many platform is using this driver without
    rsnd_dai_platform_info.
    So, this patch still supports DAI settings via SSI to keep compatible.
    It will be removed in next Linux version.

    Signed-off-by: Kuninori Morimoto
    Signed-off-by: Mark Brown

    Kuninori Morimoto
     

04 Mar, 2014

1 commit


03 Mar, 2014

1 commit


01 Mar, 2014

7 commits

  • The hda codecs all use this struct and, with an HDA platform driver,
    will be able to be built without PCI.

    Signed-off-by: Dylan Reid
    Signed-off-by: Takashi Iwai

    Dylan Reid
     
  • MUXs and virtual MUXs are almost identical, the only difference is that for
    virtual MUX there is no hardware backing register in which setting is stored.
    This patch adds code, which is similar to what we already do for DAPM mixer
    controls to support virtual mixer controls, to DAPM enum controls. The new code
    will check if the enum does a hardware backing register and skip over reading
    and writing to the register if it has not. This allows us to use the same code
    path for both MUXs and virtual MUXs and a lot of nearly identical code can be
    removed.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Mark Brown

    Lars-Peter Clausen
     
  • With the upcoming consolidation of normal MUXs and virtual MUXs we need to be
    able to distinguish between enums with and without a backing register at the
    enum level. Use the same approach as used for virtual mixer controls by setting
    the reg field of the enum to SND_SOC_NOPM for enums without a backing register.
    This patch adds a set of helper macros that can be used to define such enums.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Mark Brown

    Lars-Peter Clausen
     
  • MUXs and value MUXs are almost identical, the only difference is that a value
    MUX uses a look-up table to map from the selected control item to a register
    value, while MUXs use a direct mapping. This patch uses
    snd_soc_enum_item_to_val() and snd_soc_enum_val_to_item(), which where earlier
    introduced during the consolidation of enum and value enum controls, to hide
    this difference. This allows us to use the same code path for both MUXs and
    value MUXs and a lot of nearly duplicated code can be removed.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Mark Brown

    Lars-Peter Clausen
     
  • The implementations for enum and value enum controls are almost identical. The
    only difference is that the value enum uses an additional look-up table to map
    the control value to the register value, while the enum control uses a direct
    mapping. Enums and value enums can easily be distinguished at runtime, for value
    enums the values field of the snd_soc_enum struct contains the look-up table,
    while for enums it is NULL. This patch adds two new small helper functions
    called snd_soc_enum_item_to_val() and snd_soc_enum_val_to_item() which map
    between register value and control item. If the items field of the snd_soc_enum
    struct is NULL the function will do a direct mapping otherwise they'll use the
    look-up table to do the mapping. Using these small helper functions it is
    possible to use the same kcontrol handlers for both enums and value enums. The
    functions are added a inline functions in soc.h so they can also be used by the
    DAPM code to accomplish similar consolidation.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Mark Brown

    Lars-Peter Clausen
     
  • Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Mark Brown

    Lars-Peter Clausen
     
  • …topic/mc13783', 'fix/wm8994' and 'topic/wm8995' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into asoc-enum

    Mark Brown
     

25 Feb, 2014

1 commit

  • A few code cleanups and optimizations. In addition, drop
    snd_device_disconnect() that isn't used at all, and drop the return
    values from snd_device_free*().

    Another slight difference by this change is that now the device state
    will become always SNDRV_DEV_REGISTERED no matter whether dev_register
    ops is present or not. It's for better consistency. There should be
    no impact for the current tree, as the state isn't checked.

    Signed-off-by: Takashi Iwai

    Takashi Iwai