public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
	Rob Herring <robherring2@gmail.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Matt Porter <mporter@konsulko.com>,
	Koen Kooi <koen@dominion.thruhere.net>,
	Robert Nelson <robertcnelson@gmail.com>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Pantelis Antoniou <panto@antoniou-consulting.com>
Subject: Re: [PATCH] arm: dts: Enable beaglebone cape-manager
Date: Thu, 14 May 2015 08:39:58 -0700	[thread overview]
Message-ID: <20150514153957.GK15563@atomide.com> (raw)
In-Reply-To: <1431504292-32132-1-git-send-email-pantelis.antoniou@konsulko.com>

* Pantelis Antoniou <pantelis.antoniou@konsulko.com> [150513 01:06]:
> Enable the cape manager on the beaglebone family of boards.

I don't think we have the "ti,bone-capemgr" binding in use yet
in Linux next?

An ack from the DT people would be good to have here for the
binding.

Regards,

Tony
 
> Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
> ---
>  arch/arm/boot/dts/am335x-bone-common.dtsi | 42 +++++++++++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/am335x-bone-common.dtsi b/arch/arm/boot/dts/am335x-bone-common.dtsi
> index 236b7db..28d9764 100644
> --- a/arch/arm/boot/dts/am335x-bone-common.dtsi
> +++ b/arch/arm/boot/dts/am335x-bone-common.dtsi
> @@ -375,3 +375,45 @@
>  &sham {
>  	status = "okay";
>  };
> +
> +/* the cape manager */
> +/ {
> +	bone_capemgr {
> +		compatible = "ti,bone-capemgr";
> +		status = "okay";
> +
> +		eeprom = <&baseboard_data>;
> +
> +		/* map board revisions to compatible definitions */
> +		baseboardmaps {
> +			baseboard_beaglebone: board@0 {
> +				board-name = "A335BONE";
> +				compatible-name = "ti,beaglebone";
> +			};
> +
> +			baseboard_beaglebone_black: board@1 {
> +				board-name = "A335BNLT";
> +				compatible-name = "ti,beaglebone-black";
> +			};
> +		};
> +
> +		/* only 4 slots defined */
> +		slots {
> +			slot@0 {
> +				eeprom = <&cape0_data>;
> +			};
> +
> +			slot@1 {
> +				eeprom = <&cape1_data>;
> +			};
> +
> +			slot@2 {
> +				eeprom = <&cape2_data>;
> +			};
> +
> +			slot@3 {
> +				eeprom = <&cape3_data>;
> +			};
> +		};
> +	};
> +};
> -- 
> 1.7.12
> 

      reply	other threads:[~2015-05-14 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  8:04 [PATCH] arm: dts: Enable beaglebone cape-manager Pantelis Antoniou
2015-05-14 15:39 ` Tony Lindgren [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=20150514153957.GK15563@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=grant.likely@secretlab.ca \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mporter@konsulko.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=panto@antoniou-consulting.com \
    --cc=robertcnelson@gmail.com \
    --cc=robherring2@gmail.com \
    --cc=srinivas.kandagatla@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