Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: imx6qdl-sabresd: Provide min/max voltages for codec regulator
Date: Mon, 17 Feb 2014 10:13:56 +0800	[thread overview]
Message-ID: <20140217021354.GD9879@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <1392306839-10736-2-git-send-email-fabio.estevam@freescale.com>

On Thu, Feb 13, 2014 at 01:53:59PM -0200, Fabio Estevam wrote:
> Currently the following message is observed during boot:
> 
> wm8962-supply: no parameters
> 
> Provide min/max properties for the codec regulator.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> index a802265..086f770 100644
> --- a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
> @@ -47,6 +47,8 @@
>  			compatible = "regulator-fixed";
>  			reg = <2>;
>  			regulator-name = "wm8962-supply";
> +			regulator-min-microvolt = <4200000>;
> +			regulator-max-microvolt = <4200000>;

I guess they were omitted on purpose, because it's a backed up by a
number of supplies at different voltages.

Shawn

[1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/244470/focus=244475

>  			gpio = <&gpio4 10 0>;
>  			enable-active-high;
>  		};
> -- 
> 1.8.1.2
> 
> 

  reply	other threads:[~2014-02-17  2:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 15:53 [PATCH 1/2] ARM: dts: imx6qdl-sabresd: Add hog entry for GPIO4_10 Fabio Estevam
2014-02-13 15:53 ` [PATCH 2/2] ARM: dts: imx6qdl-sabresd: Provide min/max voltages for codec regulator Fabio Estevam
2014-02-17  2:13   ` Shawn Guo [this message]
2014-02-17  2:05 ` [PATCH 1/2] ARM: dts: imx6qdl-sabresd: Add hog entry for GPIO4_10 Shawn Guo
2014-02-17  2:11   ` Fabio Estevam
2014-02-17  2:19     ` Shawn Guo

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=20140217021354.GD9879@S2101-09.ap.freescale.net \
    --to=shawn.guo@linaro.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