1. 19 Jul, 2011 10 commits
  2. 08 Jul, 2011 9 commits
  3. 07 Jul, 2011 2 commits
  4. 01 Jul, 2011 4 commits
  5. 30 Jun, 2011 6 commits
  6. 29 Jun, 2011 9 commits
    • Kim Phillips's avatar
      crypto: caam - fix operator precedence in shared descriptor allocation · a18b989a
      Kim Phillips authored
      setkey allocates 16 bytes (CAAM_CMD_SZ *
      DESC_AEAD_SHARED_TEXT_LEN) shy of what is needed to
      store the shared descriptor, resulting in memory
      corruption.  Fix this.
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
      a18b989a
    • Linus Torvalds's avatar
      Merge branch 'kvm-updates/3.0' of git://git.kernel.org/pub/scm/virt/kvm/kvm · c017d0d1
      Linus Torvalds authored
      * 'kvm-updates/3.0' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
        KVM: x86 emulator: fix %rip-relative addressing with immediate source operand
      c017d0d1
    • Linus Torvalds's avatar
      Merge branch 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging · c7735471
      Linus Torvalds authored
      * 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging:
        i2c/pca954x: Initialize the mux to disconnected state
        i2c-taos-evm: Fix log messages
      c7735471
    • Linus Torvalds's avatar
      Merge branch 'merge' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc · 78a3cc38
      Linus Torvalds authored
      * 'merge' of git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc:
        arch/powerpc: use printk_ratelimited instead of printk_ratelimit
        powerpc/rtas-rtc: remove sideeffects of printk_ratelimit
        powerpc/pseries: remove duplicate SCSI_BNX2_ISCSI in pseries_defconfig
        powerpc/e500: fix breakage with fsl_rio_mcheck_exception
        powerpc/p1022ds: fix audio-related properties in the device tree
        powerpc/85xx: fix NAND_CMD_READID read bytes number
      78a3cc38
    • Linus Torvalds's avatar
      ahci: change 'masking port_map' printk to KERN_WARNING level · 49743170
      Linus Torvalds authored
      It's not so much an error as a warning about normal Marvell crazines.
      So don't use KERN_ERR that ends up spamming the console even in quiet
      mode, it's not _that_ critical.
      
      Explained by Jeff:
      
       "Long explanation, it's a mess:
      
        Marvell took standard AHCI, and bastardized it to include a weird mode
        whereby PATA devices appear inside the AHCI DMA and interrupt
        infrastructure you're familiar with.
      
        So, PATA devices appear via pata_marvell driver, using basic legacy
        IDE programming interface.  But SATA devices, which might also be
        attached to this chip, either work in under-performing mode or
        simply don't work at all (e.g.  newer 6 Gbps devices or port
        multiplier attachments, NCQ, ...)
      
        On the other hand, 'ahci' driver loads and works with the chip's
        attached SATA devices quite beautifully, but is completely unable to
        drive any attached PATA devices, due to the Marvell-specific
        PATA-under-AHCI interface.
      
        The "masking port_map 0x7 -> 0x3" message is the ahci driver "hiding"
        the PATA port(s) from itself, making sure it will only drive the SATA
        ports it knows how to drive."
      Acked-by: default avatarJeff Garzik <jgarzik@redhat.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      49743170
    • Petri Gynther's avatar
      i2c/pca954x: Initialize the mux to disconnected state · cd823db8
      Petri Gynther authored
      pca954x power-on default is channel 0 connected. If multiple pca954x
      muxes are connected to the same physical I2C bus, the parent bus will
      see channel 0 devices behind both muxes by default. This is bad.
      
      Scenario:
                  -- pca954x @ 0x70 -- ch 0 (I2C-bus-101) -- EEPROM @ 0x50
                  |
      I2C-bus-1 ---
                  |
                  -- pca954x @ 0x71 -- ch 0 (I2C-bus-111) -- EEPROM @ 0x50
      
      1. Load I2C bus driver: creates I2C-bus-1
      2. Load pca954x driver: creates virtual I2C-bus-101 and I2C-bus-111
      3. Load eeprom driver
      4. Try to read EEPROM @ 0x50 on I2C-bus-101. The transaction will also bleed
         onto I2C-bus-111 because pca954x @ 0x71 channel 0 is connected by default.
      
      Fix: Initialize pca954x to disconnected state in pca954x_probe()
      Signed-off-by: default avatarPetri Gynther <pgynther@google.com>
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org
      cd823db8
    • Jean Delvare's avatar
      i2c-taos-evm: Fix log messages · 9b640f2e
      Jean Delvare authored
      * Print all error and information messages even when debugging is
        disabled.
      * Don't use adapter device to log messages before it is ready.
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org
      9b640f2e
    • Benjamin Herrenschmidt's avatar
      powerpc/pseries: Move hvsi support into a library · 17bdc6c0
      Benjamin Herrenschmidt authored
      This will allow a different backend to share it
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      17bdc6c0
    • Benjamin Herrenschmidt's avatar
      powerpc/pseries: Re-implement HVSI as part of hvc_vio · 4d2bb3f5
      Benjamin Herrenschmidt authored
      On pseries machines, consoles are provided by the hypervisor using
      a low level get_chars/put_chars type interface. However, this is
      really just a transport to the service processor which implements
      them either as "raw" console (networked consoles, HMC, ...) or as
      "hvsi" serial ports.
      
      The later is a simple packet protocol on top of the raw character
      interface that is supposed to convey additional "serial port" style
      semantics. In practice however, all it does is provide a way to
      read the CD line and set/clear our DTR line, that's it.
      
      We currently implement the "raw" protocol as an hvc console backend
      (/dev/hvcN) and the "hvsi" protocol using a separate tty driver
      (/dev/hvsi0).
      
      However this is quite impractical. The arbitrary difference between
      the two type of devices has been a major source of user (and distro)
      confusion. Additionally, there's an additional mini -hvsi implementation
      in the pseries platform code for our low level debug console and early
      boot kernel messages, which means code duplication, though that low
      level variant is impractical as it's incapable of doing the initial
      protocol negociation to establish the link to the FSP.
      
      This essentially replaces the dedicated hvsi driver and the platform
      udbg code completely by extending the existing hvc_vio backend used
      in "raw" mode so that:
      
       - It now supports HVSI as well
       - We add support for hvc backend providing tiocm{get,set}
       - It also provides a udbg interface for early debug and boot console
      
      This is overall less code, though this will only be obvious once we
      remove the old "hvsi" driver, which is still available for now. When
      the old driver is enabled, the new code still kicks in for the low
      level udbg console, replacing the old mini implementation in the platform
      code, it just doesn't provide the higher level "hvc" interface.
      
      In addition to producing generally simler code, this has several benefits
      over our current situation:
      
       - The user/distro only has to deal with /dev/hvcN for the hypervisor
      console, avoiding all sort of confusion that has plagued us in the past
      
       - The tty, kernel and low level debug console all use the same code
      base which supports the full protocol establishment process, thus the
      console is now available much earlier than it used to be with the
      old HVSI driver. The kernel console works much earlier and udbg is
      available much earlier too. Hackers can enable a hard coded very-early
      debug console as well that works with HVSI (previously that was only
      supported for the "raw" mode).
      
      I've tried to keep the same semantics as hvsi relative to how I react
      to things like CD changes, with some subtle differences though:
      
       - I clear DTR on close if HUPCL is set
      
       - Current hvsi triggers a hangup if it detects a up->down transition
         on CD (you can still open a console with CD down). My new implementation
         triggers a hangup if the link to the FSP is severed, and severs it upon
         detecting a up->down transition on CD.
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      4d2bb3f5