1. 12 11月, 2014 1 次提交
  2. 10 11月, 2014 1 次提交
  3. 07 11月, 2014 12 次提交
  4. 06 11月, 2014 5 次提交
  5. 05 11月, 2014 8 次提交
    • T
      ALSA: usb-audio: Fix device_del() sysfs warnings at disconnect · 0725dda2
      Takashi Iwai 提交于
      Some USB-audio devices show weird sysfs warnings at disconnecting the
      devices, e.g.
       usb 1-3: USB disconnect, device number 3
       ------------[ cut here ]------------
       WARNING: CPU: 0 PID: 973 at fs/sysfs/group.c:216 device_del+0x39/0x180()
       sysfs group ffffffff8183df40 not found for kobject 'midiC1D0'
       Call Trace:
        [<ffffffff814a3e38>] ? dump_stack+0x49/0x71
        [<ffffffff8103cb72>] ? warn_slowpath_common+0x82/0xb0
        [<ffffffff8103cc55>] ? warn_slowpath_fmt+0x45/0x50
        [<ffffffff813521e9>] ? device_del+0x39/0x180
        [<ffffffff81352339>] ? device_unregister+0x9/0x20
        [<ffffffff81352384>] ? device_destroy+0x34/0x40
        [<ffffffffa00ba29f>] ? snd_unregister_device+0x7f/0xd0 [snd]
        [<ffffffffa025124e>] ? snd_rawmidi_dev_disconnect+0xce/0x100 [snd_rawmidi]
        [<ffffffffa00c0192>] ? snd_device_disconnect+0x62/0x90 [snd]
        [<ffffffffa00c025c>] ? snd_device_disconnect_all+0x3c/0x60 [snd]
        [<ffffffffa00bb574>] ? snd_card_disconnect+0x124/0x1a0 [snd]
        [<ffffffffa02e54e8>] ? usb_audio_disconnect+0x88/0x1c0 [snd_usb_audio]
        [<ffffffffa015260e>] ? usb_unbind_interface+0x5e/0x1b0 [usbcore]
        [<ffffffff813553e9>] ? __device_release_driver+0x79/0xf0
        [<ffffffff81355485>] ? device_release_driver+0x25/0x40
        [<ffffffff81354e11>] ? bus_remove_device+0xf1/0x130
        [<ffffffff813522b9>] ? device_del+0x109/0x180
        [<ffffffffa01501d5>] ? usb_disable_device+0x95/0x1f0 [usbcore]
        [<ffffffffa014634f>] ? usb_disconnect+0x8f/0x190 [usbcore]
        [<ffffffffa0149179>] ? hub_thread+0x539/0x13a0 [usbcore]
        [<ffffffff810669f5>] ? sched_clock_local+0x15/0x80
        [<ffffffff81066c98>] ? sched_clock_cpu+0xb8/0xd0
        [<ffffffff81070730>] ? bit_waitqueue+0xb0/0xb0
        [<ffffffffa0148c40>] ? usb_port_resume+0x430/0x430 [usbcore]
        [<ffffffffa0148c40>] ? usb_port_resume+0x430/0x430 [usbcore]
        [<ffffffff8105973e>] ? kthread+0xce/0xf0
        [<ffffffff81059670>] ? kthread_create_on_node+0x1c0/0x1c0
        [<ffffffff814a8b7c>] ? ret_from_fork+0x7c/0xb0
        [<ffffffff81059670>] ? kthread_create_on_node+0x1c0/0x1c0
       ---[ end trace 40b1928d1136b91e ]---
      
      This comes from the fact that usb-audio driver may receive the
      disconnect callback multiple times, per each usb interface.  When a
      device has both audio and midi interfaces, it gets called twice, and
      currently the driver tries to release resources at the last call.
      At this point, the first parent interface has been already deleted,
      thus deleting a child of the first parent hits such a warning.
      
      For fixing this problem, we need to call snd_card_disconnect() and
      cancel pending operations at the very first disconnect while the
      release of the whole objects waits until the last disconnect call.
      
      Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=80931Reported-and-tested-by: NTomas Gayoso <tgayoso@gmail.com>
      Reported-and-tested-by: NChris J Arges <chris.j.arges@canonical.com>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      0725dda2
    • M
      ovl: don't poison cursor · 3f822c62
      Miklos Szeredi 提交于
      ovl_cache_put() can be called from ovl_dir_reset() if the cache needs to be
      rebuilt.  We did list_del() on the cursor, which results in an Oops on the
      poisoned pointer in ovl_seek_cursor().
      Reported-by: NJordi Pujol Palomer <jordipujolp@gmail.com>
      Signed-off-by: NMiklos Szeredi <mszeredi@suse.cz>
      Tested-by: NJordi Pujol Palomer <jordipujolp@gmail.com>
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      3f822c62
    • K
      mmc: core: fix card detection regression · a31b0c6c
      Kristina Martsenko 提交于
      Since commit 89168b48 ("mmc: core: restore detect line inversion
      semantics"), the SD card on i.MX28 (and possibly other) devices isn't
      detected and booting stops at:
      
      [    4.120617] Waiting for root device /dev/mmcblk0p3...
      
      This is caused by the MMC_CAP2_CD_ACTIVE_HIGH flag being set incorrectly
      when the host controller doesn't use a GPIO for card detection (but
      instead uses a dedicated pin). In this case mmc_gpiod_request_cd() will
      return before assigning to the gpio_invert variable, leaving the
      variable uninitialized. The variable then gets used to set the flag.
      This patch fixes the issue by making sure gpio_invert is set to false
      when a GPIO isn't used. After this patch, i.MX28 boots fine.
      
      The MMC_CAP2_RO_ACTIVE_HIGH (write protect) flag is also set incorrectly
      for the exact same reason (it uses the same uninitialized variable), so
      this patch fixes that too.
      
      Fixes: 89168b48 ("mmc: core: restore detect line inversion semantics")
      Reported-by: NStefan Wahren <stefan.wahren@i2se.com>
      Signed-off-by: NKristina Martšenko <kristina.martsenko@gmail.com>
      Tested-by: NFabio Estevam <fabio.estevam@freescale.com>
      Signed-off-by: NUlf Hansson <ulf.hansson@linaro.org>
      a31b0c6c
    • H
      ALSA: hda - fix mute led problem for three HP laptops · c922c4e8
      Hui Wang 提交于
      Without the fix, the mute led can't work on these three machines.
      
      After apply this fix, these three machines will fall back on the led
      control quirk as below, and through testing, the mute led works very
      well.
      PIN_QUIRK(0x10ec0282, 0x103c, "HP", ALC269_FIXUP_HP_LINE1_MIC1_LED,
                  ALC282_STANDARD_PINS,
                  {0x12, 0x90a60140},
                  ...
      
      BugLink: https://bugs.launchpad.net/bugs/1389497Tested-by: NTieFu Chen <tienfu.chen@canonical.com>
      Cc: Kailang Yang <kailang@realtek.com>
      Cc: stable@vger.kernel.org
      Signed-off-by: NHui Wang <hui.wang@canonical.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      c922c4e8
    • L
      Merge branch 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal · a1cff6e2
      Linus Torvalds 提交于
      Pull thermal fixes from Eduardo Valentin:
       "Specifics:
         - a few code fixes improving the Exynos code base.  They remove dead
           and unreachable code.  No functional changes here
         - in Exynos code base, fixes regarding the right usage of features
           (TRIMINFO and TRIMRELOAD)
         - documentation of RCAR thermal
         - fix in the of-thermal, regarding the proper usage of of-APIs
         - fixes on thermal-core, removal of unreachable code"
      
      [ Eduardo is sending the thermal fixes on behalf of Rui Zhang this time.
        Rui is currently unable to send pull requests due to troubles with his
        machine and he's currently in a business trip ]
      
      * 'fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal:
        Thermal:Remove usless if(!result) before return tz
        thermal: exynos: fix IRQ clearing on TMU initialization
        thermal: fix multiple disbalanced device node counters
        thermal: rcar: Add binding docs for new R-Car Gen2 SoCs
        thermal: exynos: Add support for TRIM_RELOAD feature at Exynos3250
        thermal: exynos: Add support for many TRIMINFO_CTRL registers
        thermal: samsung: Exynos5260 and Exynos5420 should not use TRIM_RELOAD flag
        thermal: exynos: remove identical values from exynos*_tmu_registers structures
        thermal: exynos: remove redundant pdata checks from exynos_tmu_control()
        thermal: exynos: cache non_hw_trigger_levels in pdata
        thermal: exynos: simplify temp_to_code() and code_to_temp()
        thermal: exynos: remove redundant threshold_code checks from exynos_tmu_initialize()
        thermal: exynos: remove redundant pdata checks from exynos_tmu_initialize()
        thermal: exynos: remove dead code for HW_MODE calibration
        thermal: exynos: remove unused struct exynos_tmu_registers entries
      a1cff6e2
    • L
      Merge tag 'platform-drivers-x86-v3.18-2' of... · 9319bc1c
      Linus Torvalds 提交于
      Merge tag 'platform-drivers-x86-v3.18-2' of git://git.infradead.org/users/dvhart/linux-platform-drivers-x86
      
      Pull x86 platform drievr updates from Darren Hart:
       "A short list of patches applying quirks and new DMI matches.  These
        pass my basic build tests and have spent 4 days in linux-next"
      
      * tag 'platform-drivers-x86-v3.18-2' of git://git.infradead.org/users/dvhart/linux-platform-drivers-x86:
        quirk for Lenovo Yoga 3: no rfkill switch
        acer-wmi: Add acpi_backlight=video quirk for the Acer KAV80
        samsung-laptop: Add broken-acpi-video quirk for NC210/NC110
        asus-nb-wmi: Add wapf4 quirk for the X550VB
        toshiba_acpi: Add Toshiba TECRA A50-A to the alt keymap dmi list
      9319bc1c
    • L
      Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux · 8a97577a
      Linus Torvalds 提交于
      Pull powerpc fixes from Michael Ellerman:
       "Some more powerpc fixes if you please"
      
      * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux:
        powerpc: use device_online/offline() instead of cpu_up/down()
        powerpc/powernv: Properly fix LPC debugfs endianness
        powerpc: do_notify_resume can be called with bad thread_info flags argument
        powerpc/fadump: Fix endianess issues in firmware assisted dump handling
        powerpc: Fix section mismatch warning
      8a97577a
    • L
      Merge tag 'ftracetest-3.18-rc1' of... · 1efa82ec
      Linus Torvalds 提交于
      Merge tag 'ftracetest-3.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
      
      Pull ftracetest fix from Steven Rostedt:
       "Running the ftracetests on a machine that had the debugfs file system
        mounted in two locations caused the ftracetests to fail.  This is
        because the ftracetests script does a grep of the /proc/mounts file to
        find where the debugfs file system is mounted.  If it is mounted
        twice, then the grep returns two lines instead of just one.  This
        causes the ftracetests to get confused and fail.
      
        Use "head -1" to only return the first mount point for debugfs"
      
      * tag 'ftracetest-3.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
        ftracetest: Take the first debugfs mount found
      1efa82ec
  6. 04 11月, 2014 7 次提交
  7. 03 11月, 2014 6 次提交