linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Venkat Reddy Talla <vreddytalla@nvidia.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, ldewangan@nvidia.com,
	svelpula@nvidia.com
Subject: Re: [PATCH v2 2/2] dt-bindings: max77620: add documentation for MPOK property
Date: Mon, 21 Nov 2016 13:10:48 +0000	[thread overview]
Message-ID: <20161121131048.GD3917@dell> (raw)
In-Reply-To: <1479405276-26452-2-git-send-email-vreddytalla@nvidia.com>

On Thu, 17 Nov 2016, Venkat Reddy Talla wrote:

> Adding documentation for maxim,power-ok-control dts property
> 
> Signed-off-by: Venkat Reddy Talla <vreddytalla@nvidia.com>
> 
> ---
> Changes from V1:
>  None
> ---
>  Documentation/devicetree/bindings/mfd/max77620.txt | 12 ++++++++++++
>  1 file changed, 12 insertions(+)

For my own reference:
  Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
  
> diff --git a/Documentation/devicetree/bindings/mfd/max77620.txt b/Documentation/devicetree/bindings/mfd/max77620.txt
> index 2ad44f7..9c16d51 100644
> --- a/Documentation/devicetree/bindings/mfd/max77620.txt
> +++ b/Documentation/devicetree/bindings/mfd/max77620.txt
> @@ -106,6 +106,18 @@ Here supported time periods by device in microseconds are as follows:
>  MAX77620 supports 40, 80, 160, 320, 640, 1280, 2560 and 5120 microseconds.
>  MAX20024 supports 20, 40, 80, 160, 320, 640, 1280 and 2540 microseconds.
>  
> +-maxim,power-ok-control: configure map power ok bit
> +			1: Enables POK(Power OK) to control nRST_IO and GPIO1
> +			POK function.
> +			0: Disables POK control.
> +			if property missing, do not configure MPOK bit.
> +			If POK mapping is enabled for GPIO1/nRST_IO then,
> +			GPIO1/nRST_IO pins are HIGH only if all rails
> +			that have POK control enabled are HIGH.
> +			If any of the rails goes down(which are enabled for POK
> +			control) then, GPIO1/nRST_IO goes LOW.
> +			this property is valid for max20024 only.
> +
>  For DT binding details of different sub modules like GPIO, pincontrol,
>  regulator, power, please refer respective device-tree binding document
>  under their respective sub-system directories.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2016-11-21 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 17:54 [PATCH v2 1/2] regulator: max77620: add support to configure MPOK Venkat Reddy Talla
2016-11-17 17:54 ` [PATCH v2 2/2] dt-bindings: max77620: add documentation for MPOK property Venkat Reddy Talla
2016-11-18 14:54   ` Rob Herring
2016-11-21 13:10   ` Lee Jones [this message]
2016-11-21 13:09 ` [PATCH v2 1/2] regulator: max77620: add support to configure MPOK Lee Jones
2016-11-21 13:11   ` Lee Jones
2016-11-23 16:40     ` Mark Brown
2016-11-23 16:31 ` Applied "regulator: max77620: add support to configure MPOK" to the regulator tree Mark Brown

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=20161121131048.GD3917@dell \
    --to=lee.jones@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=svelpula@nvidia.com \
    --cc=vreddytalla@nvidia.com \
    /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).