1. 24 11月, 2011 2 次提交
  2. 23 11月, 2011 2 次提交
    • A
      regulator: TPS65910: Fix VDD1/2 voltage selector count · 780dc9ba
      Afzal Mohammed 提交于
      Count of selector voltage is required for regulator_set_voltage
      to work via set_voltage_sel. VDD1/2 currently have it as zero,
      so regulator_set_voltage won't work for VDD1/2.
      Update count (n_voltages) for VDD1/2.
      
      Output Voltage = (step value * 12.5 mV + 562.5 mV) * gain
      
      With above expr, number of voltages that can be selected is
      step value count * gain count
      
      constant for gain count will be called VDD1_2_NUM_VOLT_COARSE
      
      existing constant for step value count is VDD1_2_NUM_VOLTS,
      use VDD1_2_NUM_VOLT_FINE instead to make clear that step value
      is not the only component in deciding selectable voltage count
      Signed-off-by: NAfzal Mohammed <afzal@ti.com>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      780dc9ba
    • J
      i2c: Delete ANY_I2C_BUS · 67820021
      Jean Delvare 提交于
      Last piece of code using ANY_I2C_BUS was deleted almost 2 years ago,
      so ANY_I2C_BUS can go away as well.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      67820021
  3. 19 11月, 2011 1 次提交
    • D
      hugetlb: remove dummy definitions of HPAGE_MASK and HPAGE_SIZE · a5c86e98
      David Rientjes 提交于
      Dummy, non-zero definitions for HPAGE_MASK and HPAGE_SIZE were added in
      51c6f666 ("mm: ZAP_BLOCK causes redundant work") to avoid a divide
      by zero in generic kernel code.
      
      That code has since been removed, but probably should never have been
      added in the first place: we don't want HPAGE_SIZE to act like PAGE_SIZE
      for code that is working with hugepages, for example, when the
      dependency on CONFIG_HUGETLB_PAGE has not been fulfilled.
      
      Because hugepage size can differ from architecture to architecture, each
      is required to have their own definitions for both HPAGE_MASK and
      HPAGE_SIZE.  This is always done in arch/*/include/asm/page.h.
      
      So, just remove the dummy and dangerous definitions since they are no
      longer needed and reveals the correct dependencies.  Tested on
      architectures using the definitions with allyesconfig: x86 (even with
      thp), hppa, mips, powerpc, s390, sh3, sh4, sparc, and sparc64, and with
      defconfig on ia64.
      Signed-off-by: NDavid Rientjes <rientjes@google.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a5c86e98
  4. 18 11月, 2011 1 次提交
    • R
      PM Sleep: Do not extend wakeup paths to devices with ignore_children set · 8b258cc8
      Rafael J. Wysocki 提交于
      Commit 4ca46ff3 (PM / Sleep: Mark
      devices involved in wakeup signaling during suspend) introduced
      the power.wakeup_path field in struct dev_pm_info to mark devices
      whose children are enabled to wake up the system from sleep states,
      so that power domains containing the parents that provide their
      children with wakeup power and/or relay their wakeup signals are not
      turned off.  Unfortunately, that introduced a PM regression on SH7372
      whose power consumption in the system "memory sleep" state increased
      as a result of it, because it prevented the power domain containing
      the I2C controller from being turned off when some children of that
      controller were enabled to wake up the system, although the
      controller was not necessary for them to signal wakeup.
      
      To fix this issue use the observation that devices whose
      power.ignore_children flag is set for runtime PM should be treated
      analogously during system suspend.  Namely, they shouldn't be
      included in wakeup paths going through their children.  Since the
      SH7372 I2C controller's power.ignore_children flag is set, doing so
      will restore the previous behavior of that SOC.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NGreg Kroah-Hartman <gregkh@suse.de>
      8b258cc8
  5. 17 11月, 2011 4 次提交
  6. 16 11月, 2011 4 次提交
  7. 14 11月, 2011 1 次提交
  8. 12 11月, 2011 1 次提交
  9. 11 11月, 2011 4 次提交
  10. 10 11月, 2011 1 次提交
  11. 09 11月, 2011 2 次提交
  12. 08 11月, 2011 2 次提交
  13. 07 11月, 2011 5 次提交
  14. 05 11月, 2011 6 次提交
  15. 04 11月, 2011 4 次提交