From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Kukjin Kim <kgene@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org, Ulf Hansson <ulf.hansson@linaro.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
Subject: Re: [PATCH] ARM: dts: exynos: Fix invalid maximum voltage for buck9 supplying SD card
Date: Thu, 24 Mar 2016 09:53:32 +0000 [thread overview]
Message-ID: <20160324095332.GS2566@sirena.org.uk> (raw)
In-Reply-To: <1458807125-13580-1-git-send-email-k.kozlowski@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Thu, Mar 24, 2016 at 05:12:05PM +0900, Krzysztof Kozlowski wrote:
> buck9_reg: BUCK9 {
> regulator-name = "vdd_2.8v_ldo";
> regulator-min-microvolt = <3000000>;
> - regulator-max-microvolt = <3750000>;
> + regulator-max-microvolt = <3755000>;
> regulator-always-on;
> regulator-boot-on;
> };
Why does this regulator even have voltage constraints configured? Is
there any intention that it should ever be varied at runtime?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-24 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 8:12 [PATCH] ARM: dts: exynos: Fix invalid maximum voltage for buck9 supplying SD card Krzysztof Kozlowski
2016-03-24 9:33 ` Jaehoon Chung
2016-03-24 9:53 ` Mark Brown [this message]
2016-03-24 10:25 ` Krzysztof Kozlowski
2016-03-24 11:02 ` Mark Brown
2016-03-24 11:02 ` Mark Brown
2016-03-24 14:10 ` Markus Reichl
2016-03-25 5:45 ` Javier Martinez Canillas
2016-03-25 7:07 ` Markus Reichl
2016-03-25 7:14 ` Markus Reichl
2016-03-28 0:08 ` Krzysztof Kozlowski
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=20160324095332.GS2566@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=ulf.hansson@linaro.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).