devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <oss@buserror.net>
To: Rob Herring <robh@kernel.org>, Ran Wang <ran.wang_1@nxp.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	Zhao Chenhui <chenhui.zhao@freescale.com>,
	Li Yang <leoyang.li@nxp.com>, Paul Mackerras <paulus@samba.org>,
	linux-arm-kernel@lists.infradead.org,
	Li Yang <leoli@freescale.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] fsl_pmc: update device bindings
Date: Mon, 06 Aug 2018 19:13:49 -0500	[thread overview]
Message-ID: <fe49ef59e93842c6f2beabd130918c9262cef9fe.camel@buserror.net> (raw)
In-Reply-To: <20180416151356.r7si6higfrovl53l@rob-hp-laptop>

On Mon, 2018-04-16 at 10:13 -0500, Rob Herring wrote:
> On Wed, Apr 11, 2018 at 02:35:51PM +0800, Ran Wang wrote:
> > From: Li Yang <leoli@freescale.com>
> 
> Needs a commit msg and the subject should give some indication of what 
> the update is. And also start with "dt-bindings: ..."

This patch should also come before the patches that use the new binding.

> > -  fsl,mpc8536-pmc: Sleep specifiers consist of three cells, the third of
> > -  which will be ORed into PMCDR upon suspend, and cleared from PMCDR
> > -  upon resume.  The first two cells are as described for fsl,mpc8578-pmc.
> > -  This sleep controller only supports disabling devices during system
> > -  sleep, or permanently.
> > -
> > -  fsl,mpc8548-pmc: Sleep specifiers consist of one or two cells, the
> > -  first of which will be ORed into DEVDISR (and the second into
> > -  DEVDISR2, if present -- this cell should be zero or absent if the
> > -  hardware does not have DEVDISR2) upon a request for permanent device
> > -  disabling.  This sleep controller does not support configuring devices
> > -  to disable during system sleep (unless supported by another compatible
> > -  match), or dynamically.
> 
> You seem to be breaking backwards compatibility with this change. I 
> doubt that is okay on these platforms.

I don't think the sleep specifier stuff ever got used.

-Scott

  reply	other threads:[~2018-08-07  0:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  6:35 [PATCH v2 1/6] powerpc/pm: Fix suspend=n in menuconfig for e500mc platforms Ran Wang
2018-04-11  6:35 ` [PATCH v2 2/6] drivers/soc/fsl: add EPU FSM configuration for deep sleep Ran Wang
2018-04-11  6:35 ` [PATCH v2 3/6] powerpc/cache: add cache flush operation for various e500 Ran Wang
2018-04-11  6:35 ` [PATCH v2 4/6] powerpc/pm: add sleep and deep sleep on QorIQ SoCs Ran Wang
2018-04-11  6:35 ` [PATCH v2 5/6] powerpc:dts:pm: add power management node Ran Wang
2018-04-11  6:35 ` [PATCH v2 6/6] fsl_pmc: update device bindings Ran Wang
2018-04-16 15:13   ` Rob Herring
2018-08-07  0:13     ` Scott Wood [this message]
2018-08-08 23:01 ` [v2, 1/6] powerpc/pm: Fix suspend=n in menuconfig for e500mc platforms Scott Wood

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=fe49ef59e93842c6f2beabd130918c9262cef9fe.camel@buserror.net \
    --to=oss@buserror.net \
    --cc=chenhui.zhao@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoli@freescale.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.rutland@arm.com \
    --cc=paulus@samba.org \
    --cc=ran.wang_1@nxp.com \
    --cc=robh@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 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).