From: <Frank.Li@freescale.com>
To: lznuaa@gmail.com, shawn.guo@linaro.org,
dmitry.torokhov@gmail.com, robh+dt@kernel.org,
alexandre.belloni@free-electrons.com, linux@arm.linux.org.uk
Cc: linux-arm-kernel@lists.infradead.org,
linux-input@vger.kernel.org, rtc-linux@googlegroups.com,
devicetree@vger.kernel.org, Frank Li <Frank.Li@freescale.com>
Subject: [PATCH v4 0/6] Change snvs rtc and poweroff to use syscon add pwrkey driver
Date: Fri, 22 May 2015 22:36:33 +0800 [thread overview]
Message-ID: <1432305399-30571-1-git-send-email-Frank.Li@freescale.com> (raw)
From: Frank Li <Frank.Li@freescale.com>
Change from v3 to v4
- fix align
- change to pr_warn
Change from v2 to v3
- Keep snvs rtc compatiblity with old dts file
- use general syscon-poweroff instead of modifying snvs-poweroff.c
Change from v1 to v2
- Change simple-bus to simple-mfd
- RTC remove lock.
- RTC remove comments "These register offsets are relative to LP (Low Power) range"
- power off, remove extra space
Frank Li (5):
rtc: arm: imx: snvs: change use syscon to access register
Document: dt: fsl: snvs: change support syscon
arm: dts: imx: update snvs to use syscon access register
document: devicetree: input: imx: i.mx snvs power device tree bindings
arm: dts: imx6sx: enable snvs power key
Robin Gong (1):
input: keyboard: imx: add snvs power key driver
.../devicetree/bindings/crypto/fsl-sec4.txt | 70 +++++--
.../devicetree/bindings/input/snvs-pwrkey.txt | 1 +
arch/arm/boot/dts/imx6qdl.dtsi | 19 +-
arch/arm/boot/dts/imx6sl.dtsi | 19 +-
arch/arm/boot/dts/imx6sx.dtsi | 24 ++-
arch/arm/boot/dts/vfxxx.dtsi | 9 +-
drivers/input/keyboard/Kconfig | 11 +
drivers/input/keyboard/Makefile | 1 +
drivers/input/keyboard/snvs_pwrkey.c | 232 +++++++++++++++++++++
drivers/rtc/rtc-snvs.c | 136 ++++++------
10 files changed, 408 insertions(+), 114 deletions(-)
create mode 100644 Documentation/devicetree/bindings/input/snvs-pwrkey.txt
create mode 100644 drivers/input/keyboard/snvs_pwrkey.c
--
1.9.1
next reply other threads:[~2015-05-22 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 14:36 Frank.Li [this message]
2015-05-22 14:36 ` [PATCH v4 1/6] rtc: arm: imx: snvs: change use syscon to access register Frank.Li
2015-05-25 6:18 ` Shawn Guo
2015-05-25 6:44 ` Shawn Guo
2015-05-22 14:36 ` [PATCH v4 2/6] Document: dt: fsl: snvs: change support syscon Frank.Li
2015-05-25 6:26 ` Shawn Guo
2015-05-22 14:36 ` [PATCH v4 3/6] arm: dts: imx: update snvs to use syscon access register Frank.Li
2015-05-25 6:39 ` Shawn Guo
2015-05-22 14:36 ` [PATCH v4 4/6] input: keyboard: imx: add snvs power key driver Frank.Li
2015-05-25 7:35 ` Shawn Guo
2015-05-22 14:36 ` [PATCH v4 5/6] document: devicetree: input: imx: i.mx snvs power device tree bindings Frank.Li
[not found] ` <1432305399-30571-1-git-send-email-Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-05-22 14:36 ` [PATCH v4 6/6] arm: dts: imx6sx: enable snvs power key Frank.Li-KZfg59tc24xl57MIdRCFDg
2015-05-25 7:39 ` Shawn Guo
2015-05-25 6:47 ` [PATCH v4 0/6] Change snvs rtc and poweroff to use syscon add pwrkey driver Shawn Guo
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=1432305399-30571-1-git-send-email-Frank.Li@freescale.com \
--to=frank.li@freescale.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lznuaa@gmail.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=shawn.guo@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).