devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduardo.valentin@ti.com>
To: "Eduardo Valentin" <eduardo.valentin@ti.com>,
	"Benoît Cousson" <b-cousson@ti.com>
Cc: linux@arm.linux.org.uk, linux-pm@vger.kernel.org,
	tony@atomide.com,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	linux-kernel@vger.kernel.org, grant.likely@linaro.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv3 3/6] arm: dts: add bandgap entry for OMAP443x devices
Date: Tue, 18 Jun 2013 16:14:15 -0400	[thread overview]
Message-ID: <51C0BF97.6060900@ti.com> (raw)
In-Reply-To: <1370637968-23299-4-git-send-email-eduardo.valentin@ti.com>


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

Benoit,

On 07-06-2013 16:46, Eduardo Valentin wrote:
> This patch add the bandgap entry for OMAP4430 devices.
> 
> Cc: "Benoît Cousson" <b-cousson@ti.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: linux-omap@vger.kernel.org
> Cc: devicetree-discuss@lists.ozlabs.org
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>

Could you please have a look on this one?

> ---
>  arch/arm/boot/dts/omap443x.dtsi | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/omap443x.dtsi b/arch/arm/boot/dts/omap443x.dtsi
> index cccf39a..8d6c968 100644
> --- a/arch/arm/boot/dts/omap443x.dtsi
> +++ b/arch/arm/boot/dts/omap443x.dtsi
> @@ -24,4 +24,8 @@
>  			clock-latency = <300000>; /* From legacy driver */
>  		};
>  	};
> +	bandgap {
> +		reg = <0x4a002260 0x4 0x4a00232C 0x4>;
> +		compatible = "ti,omap4430-bandgap";
> +	};
>  };
> 


-- 
You have got to be excited about what you are doing. (L. Lamport)

Eduardo Valentin


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 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:[~2013-06-18 20:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1370637968-23299-1-git-send-email-eduardo.valentin@ti.com>
2013-06-07 20:46 ` [PATCHv3 1/6] thermal: ti-soc-thermal: use standard GPIO DT bindings Eduardo Valentin
2013-06-19  2:28   ` [PATCHv4 " Eduardo Valentin
2013-06-07 20:46 ` [PATCHv3 3/6] arm: dts: add bandgap entry for OMAP443x devices Eduardo Valentin
2013-06-18 20:14   ` Eduardo Valentin [this message]
2013-06-07 20:46 ` [PATCHv3 4/6] arm: dts: add bandgap entry for OMAP4460 devices Eduardo Valentin
2013-06-18 20:16   ` Eduardo Valentin
2013-06-19  1:11     ` Benoit Cousson

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=51C0BF97.6060900@ti.com \
    --to=eduardo.valentin@ti.com \
    --cc=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.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).