1. 08 May, 2012 2 commits
  2. 04 May, 2012 4 commits
  3. 03 May, 2012 8 commits
  4. 02 May, 2012 8 commits
  5. 01 May, 2012 8 commits
    • Stephen Warren's avatar
      USB: ehci-tegra: remove redundant gpio_set_value · 04c235c9
      Stephen Warren authored
      
      
      The immediately preceding gpio_direction_output() already set the value,
      so there's no need to repeat it. This also prevents gpio_set_value() from
      WARNing when the GPIO is sleepable (e.g. is on an I2C expander); the set
      direction API is always sleepable, but plain set_value isn't.
      
      Cc: <stable@vger.kernel.org> # v3.3
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      04c235c9
    • Alan Stern's avatar
      EHCI: update PM methods in ehci-tegra.c · ebf20de4
      Alan Stern authored
      
      
      This patch (as1547) rearranges the Power Management parts of the
      ehci-tegra driver to match the conventions used in other EHCI platform
      drivers.  In particular, the controller should not be powered down by
      the root hub's suspend routine; the controller's power level should be
      managed by the controller's own PM methods.
      
      The end result of the patch is that the standard ehci_bus_suspend()
      and ehci_bus_resume() methods can be used instead of special-purpose
      routines.  The driver now uses the standard dev_pm_ops methods instead
      of legacy power management.  Since there is no supported wakeup
      mechanism for the controller, runtime suspend is forbidden by default
      (this can be overridden via sysfs, if desired).
      
      These adjustments are needed in order to make ehci-tegra compatible
      with recent changes to the USB core.  The core now checks the root
      hub's status following bus suspend; if the controller is automatically
      powered down during bus suspend then the check will fail and the root
      hub will be resumed immediately.  Doing the controller power-down in a
      separate method avoids this problem.
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Acked-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      Tested-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ebf20de4
    • Alan Cox's avatar
      vt: Fix deadlock on scroll-lock · 84f904ec
      Alan Cox authored
      
      
      Fixing the locking accidentally replaced a race in the scroll
      lock handling with a deadlock. Turn it back into a race for
      now.
      
      The basic problem is that there are two paths into the tty
      stop/start helpers. One via the tty layer ^S/^Q handling
      where we need to take the kbd_event_lock and one via the
      special keyboard handler for fn_hold where we already hold
      it. Probably we need to split out into a separate LED lock
      but for now just go back to the race as it's a bit close
      to release.
      Reported-by: default avatarClemens Ladisch <clemens@ladisch.de>
      Cc: Jiri Kosina <jkosina@suse.cz>
      Signed-off-by: default avatarAlan Cox <alan@linux.intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      84f904ec
    • stephen hemminger's avatar
      sky2: fix receive length error in mixed non-VLAN/VLAN traffic · e072b3fa
      stephen hemminger authored
      
      
      Bug: The VLAN bit of the MAC RX Status Word is unreliable in several older
      supported chips. Sometimes the VLAN bit is not set for valid VLAN packets
      and also sometimes the VLAN bit is set for non-VLAN packets that came after
      a VLAN packet. This results in a receive length error when VLAN hardware
      tagging is enabled.
      
      Fix: Variation on original fix proposed by Mirko.
      The VLAN information is decoded in the status loop, and can be
      applied to the received SKB there. This eliminates the need for the
      separate tag field in the interface data structure. The tag has to
      be copied and cleared if packet is copied. This version checked out
      with vlan and normal traffic.
      
      Note: vlan_tx_tag_present should be renamed vlan_tag_present, but that
      is outside scope of this.
      Reported-by: default avatarMirko Lindner <mlindner@marvell.com>
      Signed-off-by: default avatarStephen Hemminger <shemminger@vyatta.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e072b3fa
    • stephen hemminger's avatar
      sky2: propogate rx hash when packet is copied · 3f42941b
      stephen hemminger authored
      
      
      When a small packet is received, the driver copies it to a new skb to allow
      reusing the full size Rx buffer. The copy was propogating the checksum offload
      but not the receive hash information. The bug is impact was mostly harmless
      and therefore not observed until reviewing this area of code.
      Signed-off-by: default avatarStephen Hemminger <shemminger@vyatta.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      3f42941b
    • Guenter Roeck's avatar
      hwmon: (coretemp) Increase CPU core limit · bdc71c9a
      Guenter Roeck authored
      
      
      CPU core ID is used to index the core_data[] array. The core ID is, however, not
      sequential; 10-core CPUS can have a core ID as high as 25. Increase the limit to
      32 to be able to deal with current CPUs.
      Signed-off-by: default avatarGuenter Roeck <guenter.roeck@ericsson.com>
      Cc: stable@vger.kernel.org # 3.0+
      Acked-by: default avatarJean Delvare <khali@linux-fr.org>
      Acked-by: default avatarDurgadoss R <durgadoss.r@intel.com>
      bdc71c9a
    • Kirill A. Shutemov's avatar
      hwmon: (coretemp) fix oops on cpu unplug · b7048711
      Kirill A. Shutemov authored
      
      
      coretemp tries to access core_data array beyond bounds on cpu unplug if
      core id of the cpu if more than NUM_REAL_CORES-1.
      
      BUG: unable to handle kernel NULL pointer dereference at 000000000000013c
      IP: [<ffffffffa00159af>] coretemp_cpu_callback+0x93/0x1ba [coretemp]
      PGD 673e5a067 PUD 66e9b3067 PMD 0
      Oops: 0000 [#1] SMP
      CPU 79
      Modules linked in: sunrpc cpufreq_ondemand acpi_cpufreq freq_table mperf bnep bluetooth rfkill ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter nf_conntrack_ipv4 nf_defrag_ipv4 ip6_tables xt_state nf_conntrack coretemp crc32c_intel asix tpm_tis pcspkr usbnet iTCO_wdt i2c_i801 microcode mii joydev tpm i2c_core iTCO_vendor_support tpm_bios i7core_edac igb ioatdma edac_core dca megaraid_sas [last unloaded: oprofile]
      
      Pid: 3315, comm: set-cpus Tainted: G        W    3.4.0-rc5+ #2 QCI QSSC-S4R/QSSC-S4R
      RIP: 0010:[<ffffffffa00159af>]  [<ffffffffa00159af>] coretemp_cpu_callback+0x93/0x1ba [coretemp]
      RSP: 0018:ffff880472fb3d48  EFLAGS: 00010246
      RAX: 0000000000000124 RBX: 0000000000000034 RCX: 00000000ffffffff
      RDX: 0000000000000000 RSI: 0000000000000046 RDI: 0000000000000246
      RBP: ffff880472fb3d88 R08: ffff88077fcd36c0 R09: 0000000000000001
      R10: ffffffff8184bc48 R11: 0000000000000000 R12: ffff880273095800
      R13: 0000000000000013 R14: ffff8802730a1810 R15: 0000000000000000
      FS:  00007f694a20f720(0000) GS:ffff88077fcc0000(0000) knlGS:0000000000000000
      CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
      CR2: 000000000000013c CR3: 000000067209b000 CR4: 00000000000007e0
      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
      DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
      Process set-cpus (pid: 3315, threadinfo ffff880472fb2000, task ffff880471fa0000)
      Stack:
       ffff880277b4c308 0000000000000003 ffff880472fb3d88 0000000000000005
       0000000000000034 00000000ffffffd1 ffffffff81cadc70 ffff880472fb3e14
       ffff880472fb3dc8 ffffffff8161f48d ffff880471fa0000 0000000000000034
      Call Trace:
       [<ffffffff8161f48d>] notifier_call_chain+0x4d/0x70
       [<ffffffff8107f1be>] __raw_notifier_call_chain+0xe/0x10
       [<ffffffff81059d30>] __cpu_notify+0x20/0x40
       [<ffffffff815fa251>] _cpu_down+0x81/0x270
       [<ffffffff815fa477>] cpu_down+0x37/0x50
       [<ffffffff815fd6a3>] store_online+0x63/0xc0
       [<ffffffff813c7078>] dev_attr_store+0x18/0x30
       [<ffffffff811f02cf>] sysfs_write_file+0xef/0x170
       [<ffffffff81180443>] vfs_write+0xb3/0x180
       [<ffffffff8118076a>] sys_write+0x4a/0x90
       [<ffffffff816236a9>] system_call_fastpath+0x16/0x1b
      Code: 48 c7 c7 94 60 01 a0 44 0f b7 ac 10 ac 00 00 00 31 c0 e8 41 b7 5f e1 41 83 c5 02 49 63 c5 49 8b 44 c4 10 48 85 c0 74 56 45 31 ff <39> 58 18 75 4e eb 1f 49 63 d7 4c 89 f7 48 89 45 c8 48 6b d2 28
      RIP  [<ffffffffa00159af>] coretemp_cpu_callback+0x93/0x1ba [coretemp]
       RSP <ffff880472fb3d48>
      CR2: 000000000000013c
      Signed-off-by: default avatarKirill A. Shutemov <kirill.shutemov@linux.intel.com>
      Cc: stable@vger.kernel.org # 3.0+
      Signed-off-by: default avatarGuenter Roeck <guenter.roeck@ericsson.com>
      b7048711
    • Russ Dill's avatar
      mfd: Fix build breakage in omap-usb-host.c · 13176a89
      Russ Dill authored
      
      
      'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue' removes the include for
      linux/gpio.h from omap-usb-host.c. This include indirectly includes plat/cpu.h
      which is required by omap-usb-host.c. Fix the build breakage by including
      it directly.
      Acked-by: default avatarKeshava Munegowda <keshava_mgowda@ti.com>
      Acked-by: default avatarKevin Hilman <khilman@ti.com>
      Tested-by: default avatarArend van Spriel <arend@broadcom.com>
      Signed-off-by: default avatarRuss Dill <Russ.Dill@ti.com>
      Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      13176a89
  6. 30 Apr, 2012 10 commits