linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] Change snvs rtc and poweroff to use syscon add pwrkey driver
Date: Wed, 20 May 2015 22:22:07 +0800	[thread overview]
Message-ID: <20150520142205.GA24844@dragon> (raw)
In-Reply-To: <CAHrpEqS5gAsu6=ut-mPwZiipqKJb=VicRooCPFhEf324kuhnDQ@mail.gmail.com>

On Tue, May 19, 2015 at 09:44:46PM -0500, Zhi Li wrote:
> On Tue, May 19, 2015 at 8:58 PM, Shawn Guo <shawnguo@kernel.org> wrote:
> > On Wed, May 20, 2015 at 01:04:35AM +0800, Frank.Li at freescale.com wrote:
> >> From: Frank Li <Frank.Li@freescale.com>
> >>
> >> 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
> >>
> >> SNVS is MPF module.
> >> include rtc, power off, ON/OFF power key
> >>
> >>   arm: imx: power-off: change to syscon to access register
> >>   rtc: arm: imx: snvs: change use syscon to access register
> >> Above two patch change existed power-off and rtc use syscon
> >>
> >>   Document: dt: fsl: snvs: change support syscon
> >>   arm: dts: imx: update snvs to use syscon access register
> >> Update dt file and document
> >>
> >>   input: keyboard: imx: add snvs power key driver
> >>   document: devicetree: input: imx: i.mx snvs power device tree bindings
> >>   arm: dts: imx6sx: enable snvs power key
> >> Added on/off key driver
> >>
> >> Frank Li (6):
> >>   arm: imx: power-off: change to syscon to access register
> >>   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
> >
> > So, the series will break existing DTBs for RTC and poweroff, right?
> > If this is unavoidable, should we at least have some warning messages
> > telling users about his breakage?
> 
> How to do that?
> Just added it commit message or need runtime warning?

runtime, so that users can know why their installed DTBs break with the
new kernel.

Shawn

  reply	other threads:[~2015-05-20 14:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 17:04 [PATCH v2 0/7] Change snvs rtc and poweroff to use syscon add pwrkey driver Frank.Li at freescale.com
2015-05-19 17:04 ` [PATCH v2 1/7] arm: imx: power-off: change to syscon to access register Frank.Li at freescale.com
2015-05-19 17:04 ` [PATCH v2 2/7] rtc: arm: imx: snvs: change use " Frank.Li at freescale.com
2015-05-19 20:46   ` Alexandre Belloni
2015-05-19 17:04 ` [PATCH v2 3/7] Document: dt: fsl: snvs: change support syscon Frank.Li at freescale.com
2015-05-19 17:04 ` [PATCH v2 4/7] arm: dts: imx: update snvs to use syscon access register Frank.Li at freescale.com
2015-05-19 17:04 ` [PATCH v2 5/7] input: keyboard: imx: add snvs power key driver Frank.Li at freescale.com
2015-05-19 17:04 ` [PATCH v2 6/7] document: devicetree: input: imx: i.mx snvs power device tree bindings Frank.Li at freescale.com
2015-05-19 17:04 ` [PATCH v2 7/7] arm: dts: imx6sx: enable snvs power key Frank.Li at freescale.com
2015-05-20  1:58 ` [PATCH v2 0/7] Change snvs rtc and poweroff to use syscon add pwrkey driver Shawn Guo
2015-05-20  2:44   ` Zhi Li
2015-05-20 14:22     ` Shawn Guo [this message]
2015-05-20 14:30       ` Zhi Li
2015-05-20 14:46         ` Joshua Clayton
2015-05-20 15:03           ` Zhi Li
2015-05-20 18:25   ` Russell King - ARM Linux
2015-05-20 18:30     ` Russell King - ARM Linux
2015-05-20 18:44       ` Zhi Li
2015-05-20 21:56         ` Russell King - ARM Linux
2015-05-21  0:20       ` Dmitry Torokhov
2015-05-21  1:16         ` Zhi Li

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=20150520142205.GA24844@dragon \
    --to=shawn.guo@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).