public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: lee.jones@linaro.org
Cc: broonie@kernel.org, sameo@linux.intel.com,
	linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
	patches@opensource.wolfsonmicro.com
Subject: [PATCH v2 0/9] wm5110 Boot Fixups
Date: Fri, 17 Apr 2015 09:42:17 +0100	[thread overview]
Message-ID: <1429260146-16694-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)

Ok so I have completed the rework to the second of the two patch
chains on this and pulled them back together into one series.

Note the main difference is I have pulled a couple patches from
the second series to the start of the chain. This is because of
patch 3 which is a bug fix for 5102 I have discovered whilst
working through this better system suspend support stuff.

Changes since v1:
 - Just updated the return of wm5110_apply_sleep_patch to use the
   ternary as per Lee's preference.

Thanks,
Charles

Charles Keepax (9):
  mfd: arizona: Use devres to manage reset GPIO
  mfd: arizona: Factor out hard reset into helper functions
  mfd: wm5102: Ensure we always boot the device fully
  mfd: arizona: Factor out SYSCLK enable from wm5102 hardware patch
  mfd: wm5110: Add register patch required for low power sleep
  regulator: arizona-ldo1: Add additional supported voltage
  mfd: wm5110: Set DCVDD voltage to 1.175V before entering sleep mode
  mfd: arizona: Add better support for system suspend
  mfd: wm5110: Add delay before releasing reset line

 drivers/mfd/arizona-core.c       |  341 ++++++++++++++++++++++++++++++++------
 drivers/regulator/arizona-ldo1.c |   15 ++
 include/linux/mfd/arizona/core.h |    1 +
 3 files changed, 302 insertions(+), 55 deletions(-)

-- 
1.7.2.5


             reply	other threads:[~2015-04-17  8:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  8:42 Charles Keepax [this message]
2015-04-17  8:42 ` [PATCH v2 1/9] mfd: arizona: Use devres to manage reset GPIO Charles Keepax
2015-04-29 12:27   ` Lee Jones
2015-04-17  8:42 ` [PATCH v2 2/9] mfd: arizona: Factor out hard reset into helper functions Charles Keepax
2015-04-29 12:26   ` Lee Jones
2015-04-17  8:42 ` [PATCH v2 3/9] mfd: wm5102: Ensure we always boot the device fully Charles Keepax
2015-04-29 12:25   ` Lee Jones
2015-04-17  8:42 ` [PATCH v2 4/9] mfd: arizona: Factor out SYSCLK enable from wm5102 hardware patch Charles Keepax
2015-04-29 12:17   ` Lee Jones
2015-04-17  8:42 ` [PATCH v2 5/9] mfd: wm5110: Add register patch required for low power sleep Charles Keepax
2015-04-17  8:42 ` [PATCH v2 6/9] regulator: arizona-ldo1: Add additional supported voltage Charles Keepax
2015-04-17  8:42 ` [PATCH v2 7/9] mfd: wm5110: Set DCVDD voltage to 1.175V before entering sleep mode Charles Keepax
2015-04-17  8:42 ` [PATCH v2 8/9] mfd: arizona: Add better support for system suspend Charles Keepax
2015-04-29 12:11   ` Lee Jones
2015-04-17  8:42 ` [PATCH v2 9/9] mfd: wm5110: Add delay before releasing reset line Charles Keepax
2015-04-29 11:54   ` Lee Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1429260146-16694-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
    --to=ckeepax@opensource.wolfsonmicro.com \
    --cc=broonie@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=sameo@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox