From: Shawn Guo <shawnguo@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: s.riedmueller@phytec.de, festevam@gmail.com,
chf.fritz@googlemail.com, robh+dt@kernel.org, linux-imx@nxp.com,
kernel@pengutronix.de, c.hemp@phytec.de, s.christ@phytec.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: dts: imx6: phycore-som: add pmic onkey device
Date: Thu, 9 Jan 2020 14:46:44 +0800 [thread overview]
Message-ID: <20200109064644.GB4456@T480> (raw)
In-Reply-To: <20191129164859.15632-3-m.felsch@pengutronix.de>
On Fri, Nov 29, 2019 at 05:48:59PM +0100, Marco Felsch wrote:
> Without the onkey device it isn't possible to power off the system using
> the X_PMIC_nONKEY signal which is routed to the SoM pin header.
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
Applied, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-09 6:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 16:48 [PATCH 1/3] ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage Marco Felsch
2019-11-29 16:48 ` [PATCH 2/3] ARM: dts: imx6: phycore-som: fix emmc supply Marco Felsch
2019-12-05 12:00 ` Stefan Riedmüller
2019-12-10 9:09 ` Marco Felsch
2019-12-12 9:00 ` Stefan Riedmüller
2019-11-29 16:48 ` [PATCH 3/3] ARM: dts: imx6: phycore-som: add pmic onkey device Marco Felsch
2020-01-07 13:48 ` Marco Felsch
2020-01-09 6:46 ` Shawn Guo [this message]
2019-12-02 10:09 ` [PATCH 1/3] ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage Stefan Riedmüller
2019-12-02 12:42 ` Marco Felsch
2019-12-02 13:55 ` Stefan Riedmüller
2019-12-02 14:14 ` Marco Felsch
2019-12-02 14:30 ` Stefan Riedmüller
2019-12-02 14:53 ` Marco Felsch
2019-12-03 8:11 ` Stefan Riedmüller
2019-12-03 8:33 ` Marco Felsch
2019-12-03 9:07 ` Stefan Riedmüller
2019-12-03 11:44 ` Lucas Stach
2019-12-03 12:37 ` Stefan Riedmüller
2019-12-05 7:19 ` Marco Felsch
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=20200109064644.GB4456@T480 \
--to=shawnguo@kernel.org \
--cc=c.hemp@phytec.de \
--cc=chf.fritz@googlemail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=m.felsch@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.christ@phytec.de \
--cc=s.riedmueller@phytec.de \
/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).