All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Shawn Guo <shawnguo@kernel.org>
Cc: a.zummo@towertech.it, Frank.Li@freescale.com,
	rtc-linux@googlegroups.com, linux-pm@vger.kernel.org,
	dmitry.torokhov@gmail.com, devicetree@vger.kernel.org,
	robh+dt@kernel.org, alexandre.belloni@free-electrons.com,
	p.zabel@pengutronix.de, linux-input@vger.kernel.org,
	lznuaa@gmail.com, shawn.guo@linaro.org,
	linux-arm-kernel@lists.infradead.org
Subject: [rtc-linux] Re: [PATCH v2 0/7] Change snvs rtc and poweroff to use syscon add pwrkey driver
Date: Wed, 20 May 2015 19:30:50 +0100	[thread overview]
Message-ID: <20150520183050.GR2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150520182540.GQ2067@n2100.arm.linux.org.uk>

On Wed, May 20, 2015 at 07:25:41PM +0100, Russell King - ARM Linux wrote:
> On Wed, May 20, 2015 at 09:58:51AM +0800, Shawn Guo wrote:
> > On Wed, May 20, 2015 at 01:04:35AM +0800, Frank.Li@freescale.com wrote:
> > > 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?
> 
> What's the justification for breaking existing DTBs?  Really, this is
> something we should strive to avoid, _and_ actually avoid by providing
> backwards compatibility.

Looking at the RTC code, it would be pretty trivial to do.

Rather than passing around struct regmap, pass around the private data
structure.

Rename the regmap_* function calls to be private accessors.  Implement
a set of new accessors - if the private data has the regmap, use the
regmap API.  Otherwise, use the old method, and print a warning that an
old DT is being used.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

-- 
-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org,
	Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org,
	rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org,
	p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
	linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	lznuaa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 0/7] Change snvs rtc and poweroff to use syscon add pwrkey driver
Date: Wed, 20 May 2015 19:30:50 +0100	[thread overview]
Message-ID: <20150520183050.GR2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150520182540.GQ2067-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>

On Wed, May 20, 2015 at 07:25:41PM +0100, Russell King - ARM Linux wrote:
> On Wed, May 20, 2015 at 09:58:51AM +0800, Shawn Guo wrote:
> > On Wed, May 20, 2015 at 01:04:35AM +0800, Frank.Li-KZfg59tc24xl57MIdRCFDg@public.gmane.org wrote:
> > > 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?
> 
> What's the justification for breaking existing DTBs?  Really, this is
> something we should strive to avoid, _and_ actually avoid by providing
> backwards compatibility.

Looking at the RTC code, it would be pretty trivial to do.

Rather than passing around struct regmap, pass around the private data
structure.

Rename the regmap_* function calls to be private accessors.  Implement
a set of new accessors - if the private data has the regmap, use the
regmap API.  Otherwise, use the old method, and print a warning that an
old DT is being used.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
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 19:30:50 +0100	[thread overview]
Message-ID: <20150520183050.GR2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150520182540.GQ2067@n2100.arm.linux.org.uk>

On Wed, May 20, 2015 at 07:25:41PM +0100, Russell King - ARM Linux wrote:
> On Wed, May 20, 2015 at 09:58:51AM +0800, Shawn Guo wrote:
> > On Wed, May 20, 2015 at 01:04:35AM +0800, Frank.Li at freescale.com wrote:
> > > 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?
> 
> What's the justification for breaking existing DTBs?  Really, this is
> something we should strive to avoid, _and_ actually avoid by providing
> backwards compatibility.

Looking at the RTC code, it would be pretty trivial to do.

Rather than passing around struct regmap, pass around the private data
structure.

Rename the regmap_* function calls to be private accessors.  Implement
a set of new accessors - if the private data has the regmap, use the
regmap API.  Otherwise, use the old method, and print a warning that an
old DT is being used.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-05-20 18:31 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 17:04 [rtc-linux] [PATCH v2 0/7] Change snvs rtc and poweroff to use syscon add pwrkey driver Frank.Li
2015-05-19 17:04 ` Frank.Li at freescale.com
2015-05-19 17:04 ` Frank.Li
2015-05-19 17:04 ` [rtc-linux] [PATCH v2 1/7] arm: imx: power-off: change to syscon to access register Frank.Li
2015-05-19 17:04   ` Frank.Li at freescale.com
2015-05-19 17:04   ` Frank.Li
2015-05-19 17:04 ` [rtc-linux] [PATCH v2 2/7] rtc: arm: imx: snvs: change use " Frank.Li
2015-05-19 17:04   ` Frank.Li at freescale.com
2015-05-19 17:04   ` Frank.Li-KZfg59tc24xl57MIdRCFDg
2015-05-19 20:46   ` [rtc-linux] " Alexandre Belloni
2015-05-19 20:46     ` Alexandre Belloni
2015-05-19 20:46     ` Alexandre Belloni
2015-05-19 17:04 ` [rtc-linux] [PATCH v2 3/7] Document: dt: fsl: snvs: change support syscon Frank.Li
2015-05-19 17:04   ` Frank.Li at freescale.com
2015-05-19 17:04   ` Frank.Li
2015-05-19 17:04 ` [rtc-linux] [PATCH v2 4/7] arm: dts: imx: update snvs to use syscon access register Frank.Li
2015-05-19 17:04   ` Frank.Li at freescale.com
2015-05-19 17:04   ` Frank.Li
2015-05-19 17:04 ` [rtc-linux] [PATCH v2 5/7] input: keyboard: imx: add snvs power key driver Frank.Li
2015-05-19 17:04   ` Frank.Li at freescale.com
2015-05-19 17:04   ` Frank.Li
2015-05-19 17:04 ` [rtc-linux] [PATCH v2 6/7] document: devicetree: input: imx: i.mx snvs power device tree bindings Frank.Li
2015-05-19 17:04   ` Frank.Li at freescale.com
2015-05-19 17:04   ` Frank.Li
2015-05-19 17:04 ` [rtc-linux] [PATCH v2 7/7] arm: dts: imx6sx: enable snvs power key Frank.Li
2015-05-19 17:04   ` Frank.Li at freescale.com
2015-05-19 17:04   ` Frank.Li
2015-05-20  1:58 ` [rtc-linux] Re: [PATCH v2 0/7] Change snvs rtc and poweroff to use syscon add pwrkey driver Shawn Guo
2015-05-20  1:58   ` Shawn Guo
2015-05-20  1:58   ` Shawn Guo
2015-05-20  2:44   ` [rtc-linux] " Zhi Li
2015-05-20  2:44     ` Zhi Li
2015-05-20  2:44     ` Zhi Li
2015-05-20 14:22     ` [rtc-linux] " Shawn Guo
2015-05-20 14:22       ` Shawn Guo
2015-05-20 14:22       ` Shawn Guo
2015-05-20 14:30       ` [rtc-linux] " Zhi Li
2015-05-20 14:30         ` Zhi Li
2015-05-20 14:30         ` Zhi Li
2015-05-20 14:46         ` [rtc-linux] " Joshua Clayton
2015-05-20 14:46           ` Joshua Clayton
2015-05-20 14:46           ` Joshua Clayton
2015-05-20 15:03           ` [rtc-linux] " Zhi Li
2015-05-20 15:03             ` Zhi Li
2015-05-20 15:03             ` Zhi Li
2015-05-20 18:25   ` [rtc-linux] " Russell King - ARM Linux
2015-05-20 18:25     ` Russell King - ARM Linux
2015-05-20 18:25     ` Russell King - ARM Linux
2015-05-20 18:30     ` Russell King - ARM Linux [this message]
2015-05-20 18:30       ` Russell King - ARM Linux
2015-05-20 18:30       ` Russell King - ARM Linux
2015-05-20 18:44       ` [rtc-linux] " Zhi Li
2015-05-20 18:44         ` Zhi Li
2015-05-20 18:44         ` Zhi Li
2015-05-20 21:56         ` [rtc-linux] " Russell King - ARM Linux
2015-05-20 21:56           ` Russell King - ARM Linux
2015-05-20 21:56           ` Russell King - ARM Linux
2015-05-21  0:20       ` [rtc-linux] " Dmitry Torokhov
2015-05-21  0:20         ` Dmitry Torokhov
2015-05-21  0:20         ` Dmitry Torokhov
2015-05-21  1:16         ` [rtc-linux] " Zhi Li
2015-05-21  1:16           ` Zhi Li
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=20150520183050.GR2067@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=Frank.Li@freescale.com \
    --cc=a.zummo@towertech.it \
    --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-pm@vger.kernel.org \
    --cc=lznuaa@gmail.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=shawn.guo@linaro.org \
    --cc=shawnguo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.