Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] dt-bindings: opp: Introduce ti-opp-supply bindings
Date: Sat, 16 Dec 2017 12:01:53 -0600	[thread overview]
Message-ID: <20171216180136.sn4fmf26vcbb56u6@rob-hp-laptop> (raw)
In-Reply-To: <20171215042528.28715-4-d-gerlach@ti.com>

On Thu, Dec 14, 2017 at 10:25:27PM -0600, Dave Gerlach wrote:
> Document the devicetree bindings that describe Texas Instruments
> opp-supply which allow a platform to describe multiple regulators and
> additional information, such as registers containing data needed to
> program aforementioned regulators.
> 
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
> ---
>  .../bindings/opp/ti-omap5-opp-supply.txt           | 63 ++++++++++++++++++++++
>  1 file changed, 63 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/opp/ti-omap5-opp-supply.txt

Acked-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2017-12-16 18:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15  4:25 [PATCH v2 0/4] PM / OPP: Introduce ti-opp-supply driver Dave Gerlach
2017-12-15  4:25 ` [PATCH v2 1/4] cpufreq: ti-cpufreq: Convert to module_platform_driver Dave Gerlach
2017-12-15  4:25 ` [PATCH v2 2/4] cpufreq: ti-cpufreq: Add support for multiple regulators Dave Gerlach
2017-12-15  4:25 ` [PATCH v2 3/4] dt-bindings: opp: Introduce ti-opp-supply bindings Dave Gerlach
2017-12-15 14:29   ` Rafael J. Wysocki
2017-12-16 10:52     ` Rafael J. Wysocki
2017-12-18 19:25       ` Dave Gerlach
2017-12-19  0:26         ` Rafael J. Wysocki
2017-12-16 18:01   ` Rob Herring [this message]
2017-12-15  4:25 ` [PATCH v2 4/4] PM / OPP: Add ti-opp-supply driver Dave Gerlach
2017-12-15  4:27 ` [PATCH v2 0/4] PM / OPP: Introduce " Viresh Kumar
2017-12-15 16:30 ` Tony Lindgren

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=20171216180136.sn4fmf26vcbb56u6@rob-hp-laptop \
    --to=robh@kernel.org \
    --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