08 Dec, 2014

22 commits


07 Dec, 2014

2 commits


06 Dec, 2014

3 commits


05 Dec, 2014

8 commits

  • Pull drm intel fixes from Dave Airlie:
    "Two intel stable fixes, that should be it from me for this round"

    * 'drm-fixes' of git://people.freedesktop.org/~airlied/linux:
    drm/i915: Unlock panel even when LVDS is disabled
    drm/i915: More cautious with pch fifo underruns

    Linus Torvalds
     
  • Pull ACPI backlight fix from Rafael Wysocki:
    "This is a simple fix for an ACPI backlight regression introduced by a
    recent commit that overlooked a corner case which should have been
    taken into account"

    * tag 'pm+acpi-3.18-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
    ACPI / video: update condition to check if device is in _DOD list

    Linus Torvalds
     
  • Silence some pch fifo underrun reports and panel locking backtraces,
    both cc: stable.

    * tag 'drm-intel-fixes-2014-12-04' of git://anongit.freedesktop.org/drm-intel:
    drm/i915: Unlock panel even when LVDS is disabled
    drm/i915: More cautious with pch fifo underruns

    Dave Airlie
     
  • Pull media fixes from Mauro Carvalho Chehab:
    "A core fix and some driver fixes:
    - regression fix in Remote Controller core affecting RC6 protocol
    handling
    - fix video buffer handling in cx23885
    - race fix in solo6x10
    - fix image selection in smiapp
    - fix reported payload size on s2255drv
    - two updates for MAINTAINERS file"

    * tag 'media/v3.18-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media:
    [media] rc-core: fix toggle handling in the rc6 decoder
    MAINTAINERS: Update mchehab's addresses
    [media] cx23885: use sg = sg_next(sg) instead of sg++
    [media] s2255drv: fix payload size for JPG, MJPEG
    [media] Update MAINTAINERS for solo6x10
    [media] solo6x10: fix a race in IRQ handler
    [media] smiapp: Only some selection targets are settable

    Linus Torvalds
     
  • A typo "header=y" was introduced by commit 7071cf7fc435 ("uapi: add
    missing network related headers to kbuild").

    Signed-off-by: Masahiro Yamada
    Cc: Stephen Hemminger
    Cc: David Miller
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Masahiro Yamada
     
  • Cadence I2C controller has bug wherein it generates invalid read transactions
    after timeout in master receiver mode. This driver does not use the HW
    timeout and this interrupt is disabled but the feature itself cannot be
    disabled. Hence, this patch writes the maximum value (0xFF) to this register.
    This is one of the workarounds to this bug and it will not avoid the issue
    completely but reduces the chances of error.

    Signed-off-by: Vishnu Motghare
    Signed-off-by: Harini Katakam
    Signed-off-by: Wolfram Sang
    Cc: stable@kernel.org

    Vishnu Motghare
     
  • According to I2C specification the NACK should be handled as follows:
    "When SDA remains HIGH during this ninth clock pulse, this is defined as the Not
    Acknowledge signal. The master can then generate either a STOP condition to
    abort the transfer, or a repeated START condition to start a new transfer."
    [I2C spec Rev. 6, 3.1.6: http://www.nxp.com/documents/user_manual/UM10204.pdf]

    Currently the Davinci i2c driver interrupts the transfer on receipt of a
    NACK but fails to send a STOP in some situations and so makes the bus
    stuck until next I2C IP reset (idle/enable).

    For example, the issue will happen during SMBus read transfer which
    consists from two i2c messages write command/address and read data:

    S Slave Address Wr A Command Code A Sr Slave Address Rd A D1..Dn A P

    The I2C client device will send NACK if it can't recognize "Command Code"
    and it's expected from I2C master to generate STP in this case.
    But now, Davinci i2C driver will just exit with -EREMOTEIO and STP will
    not be generated.

    Hence, fix it by generating Stop condition (STP) always when NACK is received.

    This patch fixes Davinci I2C in the same way it was done for OMAP I2C
    commit cda2109a26eb ("i2c: omap: query STP always when NACK is received").

    Reviewed-by: Uwe Kleine-König
    Reported-by: Hein Tibosch
    Signed-off-by: Grygorii Strashko
    Signed-off-by: Wolfram Sang
    Cc: stable@kernel.org

    Grygorii Strashko
     
  • Just like 0x1600 which got blacklisted by 66a7cbc303f4 ("ahci: disable
    MSI instead of NCQ on Samsung pci-e SSDs on macbooks"), 0xa800 chokes
    on NCQ commands if MSI is enabled. Disable MSI.

    Signed-off-by: Tejun Heo
    Reported-by: Dominik Mierzejewski
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=89171
    Cc: stable@vger.kernel.org

    Tejun Heo
     

04 Dec, 2014

5 commits

  • It appears that some SCHEDULE_USER (asm for schedule_user) callers
    in arch/x86/kernel/entry_64.S are called from RCU kernel context,
    and schedule_user will return in RCU user context. This causes RCU
    warnings and possible failures.

    This is intended to be a minimal fix suitable for 3.18.

    Reported-and-tested-by: Dave Jones
    Cc: Oleg Nesterov
    Cc: Frédéric Weisbecker
    Acked-by: Paul E. McKenney
    Signed-off-by: Andy Lutomirski
    Signed-off-by: Linus Torvalds

    Andy Lutomirski
     
  • Pull i2c bugfixes from Wolfram Sang:
    "A few driver bugfixes for 3.18"

    * 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:
    i2c: omap: fix i207 errata handling
    i2c: designware: prevent early stop on TX FIFO empty
    i2c: omap: fix NACK and Arbitration Lost irq handling

    Linus Torvalds
     
  • Pull PCI fix from Bjorn Helgaas:
    "This fixes a Tegra20 regression that we introduced during the v3.18
    merge window"

    * tag 'pci-v3.18-fixes-4' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci:
    PCI: tegra: Use physical range for I/O mapping

    Linus Torvalds
     
  • Pull devicetree bugfix from Grant Likely:
    "One more bug fix for v3.18. I debated whether or not to send you this
    merge request because we're at such a late rc. The bug isn't critical
    in that there is only one system known to be affected and the patch is
    easy to backport. The codepath is used by pretty much every DT based
    system, so there is risk a of regression (it /should/ be safe, but
    I've been bitten by stuff that should be safe before). I've had it in
    linux-next for a week and haven't received any complaints.

    I think it probably should just be merged right away rather than
    waiting for the merge window and backporting. It does fix a real bug
    and the code is theoretically safer after the change. I can't think
    of any situation where it would be dangerous to reserve the DT memory
    an extra time.

    Summary from tag:

    Single bugfix for boot failure seen in the wild. The memory reserve
    code tries to be clever about reserving the FDT, but it should just
    go ahead and reserve it unconditionally to avoid the problem of
    partial overlap described in the patch"

    * tag 'devicetree-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/glikely/linux:
    of/fdt: memblock_reserve /memreserve/ regions in the case of partial overlap

    Linus Torvalds
     
  • Pull block core regression fix from Jens Axboe:
    "Single fix for a regression introduced in this development cycle,
    where dm on top of dif/dix is broken. From Darrick Wong"

    * 'for-linus' of git://git.kernel.dk/linux-block:
    block: fix regression where bio_integrity_process uses wrong bio_vec iterator

    Linus Torvalds