devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Add eeprom information
Date: Mon, 22 Feb 2016 11:19:01 -0800	[thread overview]
Message-ID: <20160222191901.GT13417@atomide.com> (raw)
In-Reply-To: <1456159868-32416-2-git-send-email-nm@ti.com>

* Nishanth Menon <nm@ti.com> [160222 08:51]:
> Add EEPROM at 0x50 that describes the board configuration.
> This is useful for userspace programs that may need to check board
> revision and other similar information.
> 
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
>  arch/arm/boot/dts/am57xx-beagle-x15.dts | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/am57xx-beagle-x15.dts b/arch/arm/boot/dts/am57xx-beagle-x15.dts
> index 36c0fa6c362a..50312f80b972 100644
> --- a/arch/arm/boot/dts/am57xx-beagle-x15.dts
> +++ b/arch/arm/boot/dts/am57xx-beagle-x15.dts
> @@ -591,6 +591,11 @@
>  		DRVDD-supply = <&vdd_3v3>;
>  		DVDD-supply = <&aic_dvdd>;
>  	};
> +
> +	eeprom: eeprom@50 {
> +		compatible = "at,24c32";
> +		reg = <0x50>;
> +	};
>  };
>  

Applying into omap-for-v4.6/dt thanks.

Tony

  reply	other threads:[~2016-02-22 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 16:51 [PATCH 0/2] ARM: OMAP: X15: Add support for eeprom Nishanth Menon
     [not found] ` <1456159868-32416-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2016-02-22 16:51   ` [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Add eeprom information Nishanth Menon
2016-02-22 19:19     ` Tony Lindgren [this message]
2016-02-22 16:51 ` [PATCH 2/2] ARM: omap2plus_defconfig: Enable AT24 eeprom Nishanth Menon
     [not found]   ` <1456159868-32416-3-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2016-02-22 18:13     ` 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=20160222191901.GT13417@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.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).