ARM: dts: odroid-xu: Add heartbead and mmc LEDs support

Add the support for LED1 on ODROID-XU2 board.
-Blue LED will be used for heartbeat
-Green LED will be used for eMMC
-Red LED will be used for microSD

Signed-off-by: Hakjoo Kim <ruppi.kim@hardkernel.com>
ARM: odroidxu_defconfig: Enable LEDs

To provide access to LEDs enable

CONFIG_LEDS_CLASS=y
CONFIG_LEDS_GPIO=y

(LED's are available from user side under under
/sys/class/leds)

To use the motherboard LEDs to show CPU
activity...

CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
CONFIG_LEDS_TRIGGER_CPU=y
clk: exynos5410: add gate clock for i2c

Adds gate clock for i2c ip for Exynos5410 SoC.
ARM: dts: exynos5410: add i2c and hsi2c device nodes

This adds device-tree nodes for the i2c and high-speed i2c busses on
 Exynos 5410 platforms.
mfd: Add MAX77xxx series MFD driver

Support the MAX77686 and MAX77802, in an attempt to avoid code duplication.
It seems easier to have one driver that can be tweaked for new PMICs than
a core driver with different clients.

Base MFD support is provided along with interrupts. The RTC and regulator
will use this base driver.

Original-Change-Id: Ifd5c5efb8fcb3d931ac89dac30144473b37580a5
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit-int.chromium.org/35487
Reviewed-by: Doug Anderson <dianders@google.com>
Commit-Queue: Doug Anderson <dianders@google.com>
Tested-by: Doug Anderson <dianders@google.com>
(cherry picked from peach-alpha commit
	419a7a89084e5cc626696e7cf344c8c9fd9b9f29)

BUG=chrome-os-partner:19007
TEST=Build and boot on peach-pit and snow; MFD driver probes once config
option is added.

Change-Id: I36b86a326adb55aefa0ed5142c39a3e93f8795c0
[abrestic: squashed opmode enum fix]
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/56567
rtc: Add MAX77xxx series real-time-clock driver

This driver supports MAX77686 and MAX77802.

Original-Change-Id: I09b17c4186c7f6d9a391802c39ddd34953649cd2
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit-int.chromium.org/35488
Reviewed-by: Doug Anderson <dianders@google.com>
Commit-Queue: Doug Anderson <dianders@google.com>
Tested-by: Doug Anderson <dianders@google.com>
(cherry picked from peach-alpha commit
	2e699fe95678077268e9e28be1b117c3b1b094d1)

BUG=chrome-os-partner:19007
TEST=Build and boot on peach-pit and snow; RTC probes once config option is
added.

Change-Id: Iaab229a53458726a6bd8b39efd2b799d9ed2c785
[abrestic: fixed trivial Kconfig conflict; squashed range-checking fix]
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/56568
regulator: Add MAX77xxx series regulator driver

This driver supports MAX77686 and MAX77802. It does not support DVS and
SELB features of these PMICs.

Original-Change-Id: I59e1b9ac733f40e22308c8c4e8738f09ee429049
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit-int.chromium.org/35507
Reviewed-by: Doug Anderson <dianders@google.com>
Commit-Queue: Doug Anderson <dianders@google.com>
Tested-by: Doug Anderson <dianders@google.com>
(cherry picked from peach-alpha commit
	15a5c42ab9646632adcb68d4692ac9d6b68a75e6)

BUG=chrome-os-partner:19007,chrome-os-partner:18697
TEST=Build and boot on peach-pit and snow.

Change-Id: I12ee38bbc9aaf4e140a6975210e0d4fe2b53bca8
[abrestic: squashed opmode fix, ramp delay fix, addition of low-jitter
mode, and voltage select mask fix]
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/56569
Reviewed-by: Simon Glass <sjg@chromium.org>
rtc: max77xxx: fix max77802 register map

The register map for the max77802 is missing the register numbers for
RTCYEARA2 and RTCDATEA2.  Add them.

BUG=chrome-os-partner:19793
TEST=Build and boot on peach-pit.

Change-Id: I912b9283d5a47b2d562e81c3f2f439587fb3e27e
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/56890
mfd: max77xxx: use correct IRQ status and mask registers

Although the PMIC interrupt status/mask regsiters are the same for both
the max77686 and max77802, the RTC interrupt registers are different.
This moves the RTC interrupt mask and status registers out of the register
map private to the RTC driver to max77{686,802}_rtc_reg enums and adds
irq_regs and irq_mask_regs fields in struct max77xxx_dev which map from
IRQ group to IRQ status and mask regsiter, respectively.

BUG=chrome-os-partner:19793
TEST=Build and boot on peach-pit and snow.  Set an rtc alarm:
localhost ~ # echo +2 > /sys/class/rtc/rtc0/wakealarm
and (from the console output) observe that an IRQ was received:
[ 1450.054837] max77xxx-rtc max77802-rtc: max77xxx_rtc_alarm_irq:irq(11)

Change-Id: I503496ff983a23d30b3dda33dc30554a4a690840
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/56891
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
mfd: max77xxx: add suspend and resume callbacks

This adds suspend and resume callbacks to the max77xxx driver which
enable and disable the max77xxx IRQ as a wakeup source, respectively.

BUG=chrome-os-partner:19793
TEST=Build and boot on peach-pit and snow.  Suspend and resume
successfully via rtcwake:
localhost ~ # rtcwake -m mem -s 10

Change-Id: I0d8578f9efe2dee00d9fe3dc4924bf40ec6bc74d
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/56892
Reviewed-by: Simon Glass <sjg@chromium.org>
mfd: max77xxx: handle pending interrupts on resume

If we were woken by an interrupt from the max77xxx PMIC, it may still
need to be ACK'ed during resume otherwise future interrupts may not be
delivered.  Run the max77xxx IRQ handler during resume to ensure that
all pending interrupts have been ACK'ed.

BUG=chrome-os-partner:19793
TEST=Suspend/resume using rtcwake on peach-pit and snow; observe that
the RTC interrupt is always ACK'ed during resume.  In dmesg:
[   79.035426] max77xxx-rtc max77686-rtc: max77xxx_rtc_alarm_irq:irq(11)

Change-Id: I03f591fa0f5853517ed3f2fc53faf6f914aa1bac
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/57148
Reviewed-by: Simon Glass <sjg@chromium.org>
mfd: max77xxx: Support using a nonzero DVS index for BUCKs

At the moment, the max77xxx driver doesn't support the GPIO-DVS
feature of the max77686 and max77802.  The existing code always just
assumed that the DVS and SELB lines on the PMIC were hardwired to 0.
That meant that updating the voltages invloved updating "slot 1"
(index 0) of the BUCK config registers.

One downside of using slot 1 of the PMIC is that, on all boards I've
seen including exynos5420-pit, slot 1 is automatically selected at
warm reset time.  Also on all boards that I've seen, warm reset is not
communicated to the max77xxx PMIC.  That means that if we modify slot
1 and do a warm reset we'll be running at voltages that may be lower
than the initial power on voltages of the board.  This can make it
difficult for the bootloader to come up at full speed.

There is no downside to the kernel using a different slot, so we can
be a little kinder to the bootloader by allowing the kernel to specify
a different slot to run in.

Note that this change _doesn't_ enable GPIO-DVS support: it merely
changes which default DVS slot the kernel works with.  This change
doesn't preclude someone later coming along and enabling GPIO-DVS
support if they found it useful, so long as they were aware of any
assumptions that the bootloader makes about the state of slot 1 at
warm reset time.

Note also that bindings and code are based loosely on the
max8997-regulator bindings, which actually does support DVS.

BUG=chrome-os-partner:21430
TEST=Boot up the system; seems reliable.
TEST=suspend_stress_test
TEST=Run tests as per chrome-os-partner:21341

Change-Id: I33ef19a67149e487ef993e7c8d4326c2f1d90edb
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/63779
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
mfd: max77xxx: Preserve firmware voltage at bootup

In the change (ba7ece1 mfd: max77xxx: Support using a nonzero DVS
index for BUCKs) I added the feature for the kernel to use a non-zero
DVS slot.  This had the unintended side effect of ignoring the voltage
that the firmware had set the system up in--not a good idea.  Change
the regulator code to preserve the firmware's values by copying them
over to the new slot.

BUG=chrome-os-partner:21430
TEST=Manual:
Before (after a cold reset):
  dmesg | grep vdd_arm
  => [    2.632594] vdd_arm: 800 <--> 1500 mV at 1000 mV
Before (in some cases after a warm reset):
  dmesg | grep vdd_arm
  => [    2.606735] vdd_arm: 800 <--> 1500 mV at 900 mV
After (always):
  dmesg | grep vdd_arm
  => [    2.632594] vdd_arm: 800 <--> 1500 mV at 1262 mV

Change-Id: Ic7d9647912d4227c1492ca3aa10b506fcc3e41f5
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/64651
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
mfd: max77xxx: correct dvs index value calculation

This patch corrects the calculation to retrive DVS index value set by
firmware. Currently, suppose firmware set index as 1, the old code
returned value 8, which is wrong.

BUG=chrome-os-partner:21687
TEST=build and booted on peach.
     /wo this patch kernel will not boot till prompt if firmware sets other
     than DVS1.
TEST=tested with other infight firmware CLs, where firmware use DVS slot2
TEST=suspend_stress_test over 20 times and multiple warmreset.
TEST=put some custom prints in driver and by chaning various DVS slot in
     firmware. can see kernel reads it right.

Change-Id: I39779bdd1f57d572411403240350598a911529fd
Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
Signed-off-by: Leela Krishna Amudala <l.krishna@samsung.com>
Signed-off-by: Rajeshwari S Shinde <rajeshwari.s@samsung.com>
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/65699
max77xxx: always use separate PMIC and RTC regmaps

We currently only use two separate regmaps on the max77686 since the
RTC is at a different I2C address.  To simplify regcache handling, make
the max77802 use separate regmaps as well.

BUG=chrome-os-partner:22964
TEST=mem_stress_switcher to test voltage scaling, rtcwake to test RTC
functionality.

Change-Id: I03e74ea0bd72f84ac39a75cd5266f1c5ab65e691
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/170998
Reviewed-by: Doug Anderson <dianders@chromium.org>
max77xxx: enable register caching

Enable regcache for the main (PMIC) regmap on the max77xxx MFDs.

BUG=chrome-os-partner:22964
TEST=mem_stress_switcher to test voltage scaling, rtcwake to test RTC
functionality.  Using ftrace, check that regulator_set_voltage() times
decrease to ~350us from ~1200us.

Change-Id: I4d400e3612fe3dab36bc1ea5222d7e8702a71399
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/170999
Reviewed-by: Doug Anderson <dianders@chromium.org>
rtc: max77xxx: enable register caching

Enable regcache for the RTC regmap on the max77xxx MFDs.

BUG=chrome-os-partner:22964
TEST=Reported time/date are correct and get updated, RTC wake
alarms still work on Snow and Pit.

Change-Id: I59b2136c1c306bd36f64ef60deff8cb9f27bc5e7
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/171100
Reviewed-by: Doug Anderson <dianders@chromium.org>
max77xxx: Add const to several structures

There are several constant structures that are never touched but
weren't marked "const".  Fix that.  This could allow the compiler to
optimize a little better.

BUG=None
TEST=Compile and boot

Change-Id: I73fe225ce6638004011b4e2f53e637157f7d2894
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/171152
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Commit-Queue: Andrew Bresticker <abrestic@chromium.org>
max77xxx: use devm_regmap_init_i2c()

BUG=chrome-os-partner:22994
TEST=PMIC/RTC still work

Change-Id: Id62f602888973540f641d14e66e493ef6e046d9c
Signed-off-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/171093
Reviewed-by: Doug Anderson <dianders@chromium.org>
max77xxx: Use irq_set_parent; don't claim to be an edge interrupt

The irq_set_chip_and_handler() takes a function that's supposed to be
the interrupt handler, but this function is in practice never really
called in the case of IRQ Domains.

It's probably a good thing that it's never really called because we
were passing a totally bogus function.  The handle_edge_irq() will
unconditionally call our ack() function which we define as NULL.

I say "never really" because there's one place where the function is
called.  ...and that's causing a crash.  The function is called if we
don't have a "parent" and we're resending a deffered IRQ at resume
time (see resend_irqs()).

Fix the resume time crash in two ways:

* Use irq_set_parent() which will make the resume-time code call the
  parent handler, not the one passed to irq_set_chip_and_handler().
  This now makes it so that the function passed is _actually_ never
  called.  The irq_set_parent() was added specifically to address this
  case.

* Pass handle_simple_irq() instead of handle_edge_irq().  This is more
  benign so if it's called we'll get a warning like:
    Primary handler called for nested irq X

BUG=chrome-os-partner:27224
TEST=suspend_stress_test
TEST=Patch in Ifd370b79689bf13de359d640a83bbf8c5b5bed52 and no longer
see crashes.

Change-Id: Ied036db9d9426bfaea6ee47edde8ca79ae698aac
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/191961
Reviewed-by: Olof Johansson <olofj@chromium.org>