1. 20 Jun, 2012 2 commits
  2. 18 Jun, 2012 5 commits
  3. 13 Jun, 2012 1 commit
  4. 12 Jun, 2012 4 commits
  5. 11 Jun, 2012 8 commits
  6. 09 Jun, 2012 1 commit
  7. 08 Jun, 2012 6 commits
    • Steven Newbury's avatar
      ALSA: hda - HDMI Audio init all connectors when VGA-switcheroo is off · 8393ec4a
      Steven Newbury authored
      
      
      When VGA_SWITCHEROO support is enabled hda_intel initialises the HDMI
      audio device on the current VGA device.  When it's not enabled it only
      initialises the HDMI device on the default VGA adaptor, this means
      secondary cards get no audio support which is very unhelpful for
      multi-seat!
      
      With this patch, when SUPPORT_VGA_SWITCHEROO is disabled hda_intel
      initialises all HDMI audio devices, not just the default VGA.
      
      [minor optimizations by tiwai]
      Signed-off-by: default avatarSteven Newbury <steve@snewbury.org.uk>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      8393ec4a
    • Takashi Iwai's avatar
      vga_switcheroo: Fix error without CONFIG_VGA_SWITCHEROO · 505cff00
      Takashi Iwai authored
      
      
      Fix a typo that is built only when CONFIG_VGA_SWITCHEROO=n.
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      505cff00
    • Takashi Iwai's avatar
      ALSA: hda - Fix uninitialized HDMI controllers with VGA-switcheroo · 12b78a7f
      Takashi Iwai authored
      
      
      When VGA-switcheroo is built in but unused on systems with multiple
      graphics cards, the initializations of non-default graphics cards are
      skipped and never enabled (because the switcheroo is activated only
      when the controller supports).  The current behavior is for avoiding
      the system lockup by accessing the disabled GPU, but due to the recent
      change in VGA-switcheroo, it determines the state simply by checking
      with the default VGA device.  This is the culprit.
      
      Now with the new vga_switcheroo_get_client_state(), we can know the
      initial state of the bound GPU, thus can determine the initial audio
      client state more correctly.
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      12b78a7f
    • Takashi Iwai's avatar
      vga_switcheroo: Add a helper function to get the client state · c8e9cf7b
      Takashi Iwai authored
      
      
      Add vga_switcheroo_get_client_state() to get the current state of the
      client.  This is necessary to determine the proper initial state of
      audio clients in HD-audio driver.
      Acked-by: default avatarDave Airlie <airlied@redhat.com>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      c8e9cf7b
    • Takashi Iwai's avatar
      ALSA: usb-audio: Fix substream assignments · 8260ef07
      Takashi Iwai authored
      In 3.5 kernel, the endpoint is assigned dynamically for the
      substreams, but the PCM assignment still checks the presence of the
      endpoint pointer.  This ended up in duplicated PCM substream creations
      at probing time, resulting in kernel warnings like:
      
      WARNING: at fs/proc/generic.c:586 proc_register+0x169/0x1a6()
      Pid: 1152, comm: modprobe Not tainted 3.5.0-rc1-00110-g71fae7e7
      
       #2
      Call Trace:
       [<ffffffff8102a400>] warn_slowpath_common+0x83/0x9c
       [<ffffffff8102a4bc>] warn_slowpath_fmt+0x46/0x48
       [<ffffffff813829ad>] ? add_preempt_count+0x39/0x3b
       [<ffffffff811292f0>] proc_register+0x169/0x1a6
       [<ffffffff8112962e>] create_proc_entry+0x74/0x8c
       [<ffffffffa018eb63>] snd_info_register+0x3e/0xc3 [snd]
       [<ffffffffa01fde2e>] snd_pcm_new_stream+0xb1/0x404 [snd_pcm]
       [<ffffffffa024861f>] snd_usb_add_audio_stream+0xd2/0x230 [snd_usb_audio]
       [<ffffffffa0241d33>] ? snd_usb_parse_audio_format+0x252/0x34f [snd_usb_audio]
       [<ffffffff810d6b17>] ? kmem_cache_alloc_trace+0xab/0xbb
       [<ffffffffa0248c29>] snd_usb_parse_audio_interface+0x4ac/0x567 [snd_usb_audio]
       [<ffffffffa023f0ff>] snd_usb_create_stream+0xe9/0x125 [snd_usb_audio]
       [<ffffffffa023f9b1>] usb_audio_probe+0x62a/0x72c [snd_usb_audio]
       .....
      
      This patch fixes the regression by checking the fixed endpoint number
      for each substream instead of the endpoint pointer.
      Reported-and-tested-by: default avatarJamie Heilman <jamie@audible.transient.net>
      Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      8260ef07
    • Stephen Warren's avatar
      ASoC: tegra: add MODULE_DEVICE_TABLE to tegra30_ahub · 69c5b753
      Stephen Warren authored
      
      
      This allows the module to automatically load when instantiated from
      device tree.
      Signed-off-by: Stephen Warren's avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      69c5b753
  8. 07 Jun, 2012 3 commits
  9. 05 Jun, 2012 2 commits
  10. 04 Jun, 2012 2 commits
  11. 03 Jun, 2012 2 commits
  12. 02 Jun, 2012 4 commits
    • Joe Thornber's avatar
      dm thin: provide userspace access to pool metadata · cc8394d8
      Joe Thornber authored
      This patch implements two new messages that can be sent to the thin
      pool target allowing it to take a snapshot of the _metadata_.  This,
      read-only snapshot can be accessed by userland, concurrently with the
      live target.
      
      Only one metadata snapshot can be held at a time.  The pool's status
      line will give the block location for the current msnap.
      
      Since version 0.1.5 of the userland thin provisioning tools, the
      thin_dump program displays the msnap as follows:
      
          thin_dump -m <msnap root> <metadata dev>
      
      Available here: https://github.com/jthornber/thin-provisioning-tools
      
      Now that userland can access the metadata we can do various things
      that have traditionally been kernel side tasks:
      
           i) Incremental backups.
      
           By using metadata snapshots we can work out what blocks have
           changed over time.  Combined with data snapshots we can ensure
           the data doesn't change while we back it up.
      
           A short proof of concept script can be found here:
      
           https://github.com/jthornber/thinp-test-suite/blob/master/incremental_backup_example.rb
      
      
      
           ii) Migration of thin devices from one pool to another.
      
           iii) Merging snapshots back into an external origin.
      
           iv) Asyncronous replication.
      Signed-off-by: default avatarJoe Thornber <ejt@redhat.com>
      Signed-off-by: default avatarAlasdair G Kergon <agk@redhat.com>
      cc8394d8
    • Mike Snitzer's avatar
      dm thin: use slab mempools · a24c2569
      Mike Snitzer authored
      
      
      Use dedicated caches prefixed with a "dm_" name rather than relying on
      kmalloc mempools backed by generic slab caches so the memory usage of
      thin provisioning (and any leaks) can be accounted for independently.
      Signed-off-by: default avatarMike Snitzer <snitzer@redhat.com>
      Signed-off-by: default avatarAlasdair G Kergon <agk@redhat.com>
      a24c2569
    • Mikulas Patocka's avatar
      dm mpath: allow ioctls to trigger pg init · 35991652
      Mikulas Patocka authored
      
      
      After the failure of a group of paths, any alternative paths that
      need initialising do not become available until further I/O is sent to
      the device.  Until this has happened, ioctls return -EAGAIN.
      
      With this patch, new paths are made available in response to an ioctl
      too.  The processing of the ioctl gets delayed until this has happened.
      
      Instead of returning an error, we submit a work item to kmultipathd
      (that will potentially activate the new path) and retry in ten
      milliseconds.
      
      Note that the patch doesn't retry an ioctl if the ioctl itself fails due
      to a path failure.  Such retries should be handled intelligently by the
      code that generated the ioctl in the first place, noting that some SCSI
      commands should not be retried because they are not idempotent (XOR write
      commands).  For commands that could be retried, there is a danger that
      if the device rejected the SCSI command, the path could be errorneously
      marked as failed, and the request would be retried on another path which
      might fail too.  It can be determined if the failure happens on the
      device or on the SCSI controller, but there is no guarantee that all
      SCSI drivers set these flags correctly.
      Signed-off-by: default avatarMikulas Patocka <mpatocka@redhat.com>
      Signed-off-by: default avatarAlasdair G Kergon <agk@redhat.com>
      35991652
    • Mike Christie's avatar
      dm mpath: delay retry of bypassed pg · f220fd4e
      Mike Christie authored
      
      
      If I/O needs retrying and only bypassed priority groups are available,
      set the pg_init_delay_retry flag to wait before retrying.
      
      If, for example, the reason for the bypass is that the controller is
      getting reset or there is a firmware upgrade happening, retrying right
      away would cause a flood of log messages and retries for what could be a
      few seconds or even several minutes.
      Signed-off-by: default avatarMike Christie <michaelc@cs.wisc.edu>
      Acked-by: default avatarMike Snitzer <snitzer@redhat.com>
      Signed-off-by: default avatarAlasdair G Kergon <agk@redhat.com>
      f220fd4e