linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 22:56:15 +0100	[thread overview]
Message-ID: <20150520215615.GZ2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAHrpEqSngMgOj5Bjp0XWpw9CJCjoiU63iRuAX3Zw_aEO+-5RHg@mail.gmail.com>

On Wed, May 20, 2015 at 01:44:58PM -0500, Zhi Li wrote:
> On Wed, May 20, 2015 at 1:30 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > 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.
> 
> This method work.  But code will become ugly and complex. I seach
> whole dts tree.
> Only imx6 use this driver.
> 
> Does it really valuable to keep compatiblity with cost of complex driver code?

Let me put this a different way.

Would you be upset if you installed a new kernel, rebooted and found that
the system then fscked your filesystem, stamping a date of 1 Jan 1970
on it.  Then you use a later dtb, and you have to go through another
fsck of your filesystem because it's apparently been more than "31 days"
or so since it was last fscked, and all this caused by the RTC vanishing
because we couldn't be bothered with backward compatibility?

There are real products out there which use iMX6 today.  In production,
being sold.

Do not break existing DTBs unless there really is no other choice.

And I don't think it makes the code ugly, though it does make it _slightly_
more complex.  That's a price worth paying for keeping stuff working.

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

  reply	other threads:[~2015-05-20 21:56 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
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 [this message]
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=20150520215615.GZ2067@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).