linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
	fabio.estevam@nxp.com, Anson.Huang@nxp.com,
	kernel@pengutronix.de, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: pfuze100: add optional disable switch-regulators binding
Date: Fri, 13 Jul 2018 16:03:14 +0100	[thread overview]
Message-ID: <20180713150314.GD16228@sirena.org.uk> (raw)
In-Reply-To: <20180713125002.24331-2-m.felsch@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

On Fri, Jul 13, 2018 at 02:50:01PM +0200, Marco Felsch wrote:

> +Optional properties:
> +- fsl,pfuze-support-disable: Boolean, if present disable all unused switch
> +  regulators to save power consumption. Attention, till 4.18 these regulators

The property name sounds like it affects all the regulators but really
it's just the sw ones - how about adding -sw at the end?  Bit of a
bikeshed but it does end up in an ABI.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-07-14 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 12:50 [PATCH v2 0/2] Re-Enable support to disable switch regulators Marco Felsch
2018-07-13 12:50 ` [PATCH v2 1/3] dt-bindings: pfuze100: add optional disable switch-regulators binding Marco Felsch
2018-07-13 15:03   ` Mark Brown [this message]
2018-07-16  7:25     ` Marco Felsch
2018-07-18 12:09       ` Mark Brown
2018-07-16 17:55   ` Rob Herring
2018-07-18 14:58     ` Marco Felsch
2018-07-13 12:50 ` [PATCH v2 2/3] regulator: pfuze100: add support to en-/disable switch regulators 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=20180713150314.GD16228@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Anson.Huang@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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).