linux-kernel - [PATCH v2 0/5] wm5110 Boot Fixups Part 2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1427216396-15517-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
Date:	Tue, 24 Mar 2015 16:59:51 +0000
From:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To:	lee.jones@...aro.org
Cc:	sameo@...ux.intel.com, broonie@...nel.org,
	patches@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/5] wm5110 Boot Fixups Part 2

Hi,

This series replaces the reset patch Mark commented on in the
early versions (see [1]) of the wm5110 boot series being reviewed
at the moment.

Basically, this series allows the CODEC to completely power
off if nothing is using it. This should cover the case where
system suspend powers the regulators down causing a second cold
boot.

NOTE: This series is dependent on the other series being reviewed
starting with:

mfd: arizona: Factor out SYSCLK enable from wm5102 hardware patch

Thanks,
Charles

Changes since v1:
 - Use devres for the reset GPIO

[1] https://lkml.org/lkml/2015/3/16/811

Charles Keepax (5):
  mfd: arizona: Use devres to manage reset GPIO
  mfd: wm5102: Move check for custom boot into arizona_wait_for_boot
  mfd: arizona: Factor out hard reset into helper functions
  mfd: arizona: Add better support for system suspend
  mfd: wm5110: Add delay before releasing reset line

 drivers/mfd/arizona-core.c       |  143 +++++++++++++++++++++++++++-----------
 include/linux/mfd/arizona/core.h |    1 +
 2 files changed, 103 insertions(+), 41 deletions(-)

-- 
1.7.2.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/