1. 17 Sep, 2012 1 commit
    • Gyungoh Yoo's avatar
      mfd: Add MAX8907 core driver · a91d2f8d
      Gyungoh Yoo authored
      The MAX8907 is an I2C-based power-management IC containing voltage
      regulators, a reset controller, a real-time clock, and a touch-screen
      controller.
      
      The original driver was written by:
      * Gyungoh Yoo <jack.yoo@maxim-ic.com>
      
      Various fixes and enhancements by:
      * Jin Park <jinyoungp@nvidia.com>
      * Tom Cherry <tcherry@nvidia.com>
      * Prashant Gaikwad <pgaikwad@nvidia.com>
      * Dan Willemsen <dwillemsen@nvidia.com>
      * Laxman Dewangan <ldewangan@nvidia.com>
      
      During upstreaming, I (swarren):
      * Converted to regmap.
      * Converted to regmap-irq.
      * Allowed probing from device tree.
      * Renamed from max8907c->max8907, since the driver covers at least the
        C and B revisions.
      * General cleanup.
      Signed-off-by: default avatarGyungoh Yoo <jack.yoo@maxim-ic.com>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com> #v3
      Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      a91d2f8d
  2. 15 Sep, 2012 3 commits
  3. 14 Sep, 2012 11 commits
  4. 11 Sep, 2012 11 commits
  5. 23 Aug, 2012 1 commit
    • Feng Tang's avatar
      mfd: lpc_ich: Fix a 3.5 kernel regression for iTCO_wdt driver · 092369ef
      Feng Tang authored
      There are many reports (including 2 of my machines) that iTCO_wdt watchdog
      driver fails to be initialized in 3.5 kernel with error message like:
      
      [    5.265175] ACPI Warning: 0x00001060-0x0000107f SystemIO conflicts with Region \_SB_.PCI0.LPCB.TCOI 1 (20120320/utaddress-251)
      [    5.265192] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
      [    5.265206] lpc_ich: Resource conflict(s) found affecting iTCO_wdt
      
      The root cause the iTCO_wdt driver in 3.4 probes the HW IO resource from
      LPC's PCI config space, while in 3.5 kernel it relies on lpc_ich driver
      for the probe, which adds a new acpi_check_resource_conflict() check, and
      give up the probe if there is any conflict with ACPI.
      
      Fix it by removing all the checks for iTCO_wdt to keep the same behavior as
      3.4 kernel.
      https://bugzilla.kernel.org/show_bug.cgi?id=44991
      
      Actually the same check could be removed for the gpio-ich in lpc_ich.c,
      but I'm not sure if it will cause problems.
      Signed-off-by: default avatarFeng Tang <feng.tang@intel.com>
      Cc: Aaron Sierra <asierra@xes-inc.com>
      Cc: Wim Van Sebroeck <wim@iguana.be>
      Cc: Len Brown <len.brown@intel.com>
      Cc: Bob Moore <robert.moore@intel.com>
      Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      092369ef
  6. 22 Aug, 2012 1 commit
    • AnilKumar Ch's avatar
      mfd: Move tps65217 regulator plat data handling to regulator · 817bb7fb
      AnilKumar Ch authored
      Regulator platform data handling was mistakenly added to MFD
      driver. So we will see build errors if we compile MFD drivers
      without CONFIG_REGULATOR. This patch moves regulator platform
      data handling from TPS65217 MFD driver to regulator driver.
      
      This makes MFD driver independent of REGULATOR framework so
      build error is fixed if CONFIG_REGULATOR is not set.
      
      drivers/built-in.o: In function `tps65217_probe':
      tps65217.c:(.devinit.text+0x13e37): undefined reference
      to `of_regulator_match'
      
      This patch also fix allocation size of tps65217 platform data.
      Current implementation allocates a struct tps65217_board for each
      regulator specified in the device tree. But the structure itself
      provides array of regulators so one instance of it is sufficient.
      Signed-off-by: default avatarAnilKumar Ch <anilkumar@ti.com>
      817bb7fb
  7. 16 Aug, 2012 11 commits
  8. 15 Aug, 2012 1 commit