1. 17 7月, 2014 2 次提交
  2. 16 7月, 2014 1 次提交
  3. 15 7月, 2014 7 次提交
  4. 07 7月, 2014 4 次提交
  5. 05 7月, 2014 1 次提交
    • B
      ASoC: add RT286 CODEC driver · 07cf7cba
      Bard Liao 提交于
      This patch adds Realtek ALC286 codec driver.
      
      ALC286 is a dual mode codec, which can run as HD-A or I2S mode.
      It is controlled by HD-A verb commands via I2C protocol.
      The following is the I/O difference between ALC286 and general I2S codecs.
      1. A HD-A verb command contains three parts, NID, VID, and PID.
         And an I2S command contains only two parts: address and data.
      2. Not only the register address is written, but the read command also
         includes the entire write command.
      3. rt286 uses different registers for read and write the same bits.
      
      We map verb command to regmap structure. However, we read most registers from
      cache to prevent the asymmetry read/write issue in rt286.
      Signed-off-by: NBard Liao <bardliao@realtek.com>
      Signed-off-by: NGustaw Lewandowski <gustaw.lewandowski@intel.com>
      Signed-off-by: NMark Brown <broonie@linaro.org>
      07cf7cba
  6. 24 6月, 2014 1 次提交
  7. 23 6月, 2014 2 次提交
  8. 22 6月, 2014 2 次提交
  9. 21 6月, 2014 5 次提交
  10. 13 6月, 2014 3 次提交
  11. 12 6月, 2014 3 次提交
  12. 10 6月, 2014 1 次提交
  13. 09 6月, 2014 2 次提交
  14. 06 6月, 2014 4 次提交
  15. 05 6月, 2014 1 次提交
  16. 04 6月, 2014 1 次提交
    • A
      ALSA: seq: Continue broadcasting events to ports if one of them fails · 27423257
      Adam Goode 提交于
      Sometimes PORT_EXIT messages are lost when a process is exiting.
      This happens if you subscribe to the announce port with client A,
      then subscribe to the announce port with client B, then kill client A.
      Client B will not see the PORT_EXIT message because client A's port is
      closing and is earlier in the announce port subscription list. The
      for each loop will try to send the announcement to client A and fail,
      then will stop trying to broadcast to other ports. Killing B works fine
      since the announcement will already have gone to A. The CLIENT_EXIT
      message does not get lost.
      
      How to reproduce problem:
      
      *** termA
      $ aseqdump -p 0:1
        0:1   Port subscribed            0:1 -> 128:0
      
      *** termB
      $ aseqdump -p 0:1
      
      *** termA
        0:1   Client start               client 129
        0:1   Port start                 129:0
        0:1   Port subscribed            0:1 -> 129:0
      
      *** termB
        0:1   Port subscribed            0:1 -> 129:0
      
      *** termA
      ^C
      
      *** termB
        0:1   Client exit                client 128
         <--- expected Port exit as well (before client exit)
      Signed-off-by: NAdam Goode <agoode@google.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      27423257