public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Priit Laes <plaes@plaes.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-sunxi@googlegroups.com,
	linux-kernel@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
	Rob Herring <robh+dt@kernel.org>, Priit Laes <priit.laes@paf.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: sun7i: olimex-lime2: Add regulators for GPIO banks
Date: Wed, 27 Feb 2019 10:24:25 +0100	[thread overview]
Message-ID: <20190227092425.ombbxgnn7ct2vkqj@flea> (raw)
In-Reply-To: <20190226141525.1039-1-plaes@plaes.org>


[-- Attachment #1.1: Type: text/plain, Size: 524 bytes --]

On Tue, Feb 26, 2019 at 04:15:25PM +0200, Priit Laes wrote:
> From: Priit Laes <priit.laes@paf.com>
> 
> Make sure that A20 Olimex Lime2 pin bank regulators are
> properly represented.
> 
> While pin banks A, B and F are connected to 3.3V static
> regulator, pin banks E and G tied with LDO3 and LDO4 regulators
> with 2.8V reference.
> 
> Signed-off-by: Priit Laes <priit.laes@paf.com>

Queued for 5.2, thanks!
Maxime

-- 
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-02-27  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 14:15 [PATCH] ARM: dts: sun7i: olimex-lime2: Add regulators for GPIO banks Priit Laes
2019-02-27  9:24 ` Maxime Ripard [this message]

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=20190227092425.ombbxgnn7ct2vkqj@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=mark.rutland@arm.com \
    --cc=plaes@plaes.org \
    --cc=priit.laes@paf.com \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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