linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: omap: pass minimal SoC/board data for UART from dt
Date: Wed, 16 Nov 2011 19:04:27 -0600	[thread overview]
Message-ID: <4EC45D9B.5020006@gmail.com> (raw)
In-Reply-To: <1321441346-19591-4-git-send-email-rnayak@ti.com>

On 11/16/2011 05:02 AM, Rajendra Nayak wrote:
> Pass minimal data needed for console boot, from dt, for
> OMAP4 panda/sdp and OMAP3 beagle boards, and get rid of the
> static initialization from generic board file.
> 
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> ---
>  arch/arm/boot/dts/omap3-beagle.dts  |   17 +++++++++++++++++
>  arch/arm/boot/dts/omap3.dtsi        |   27 +++++++++++++++++++++++++++
>  arch/arm/boot/dts/omap4-panda.dts   |   17 +++++++++++++++++
>  arch/arm/boot/dts/omap4-sdp.dts     |   17 +++++++++++++++++
>  arch/arm/boot/dts/omap4.dtsi        |   24 ++++++++++++++++++++++++
>  arch/arm/mach-omap2/board-generic.c |    1 -
>  6 files changed, 102 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/omap3-beagle.dts b/arch/arm/boot/dts/omap3-beagle.dts
> index 9486be6..4c8f11e 100644
> --- a/arch/arm/boot/dts/omap3-beagle.dts
> +++ b/arch/arm/boot/dts/omap3-beagle.dts
> @@ -27,3 +27,20 @@
>  		reg = <0x80000000 0x20000000>; /* 512 MB */
>  	};
>  };
> +
> +&uart1 {
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart2 {
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart3 {
> +	ti,console_hwmod;
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart4 {
> +	clock-frequency = <48000000>;
> +};
> diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
> index d202bb5..ea591c5 100644
> --- a/arch/arm/boot/dts/omap3.dtsi
> +++ b/arch/arm/boot/dts/omap3.dtsi
> @@ -13,6 +13,13 @@
>  / {
>  	compatible = "ti,omap3430", "ti,omap3";
>  
> +	aliases {
> +		uart1 = &uart1;
> +		uart2 = &uart2;
> +		uart3 = &uart3;
> +		uart4 = &uart4;
> +	};
> +
>  	cpus {
>  		cpu at 0 {
>  			compatible = "arm,cortex-a8";
> @@ -59,5 +66,25 @@
>  			interrupt-controller;
>  			#interrupt-cells = <1>;
>  		};
> +
> +		uart1: uart at 1 {

Use the generic name serial and the address: uart1: serial at 1234abcd

> +			compatible = "ti,omap-uart";
> +			ti,hwmods = "uart1";
> +		};
> +
> +		uart2: uart at 2 {
> +			compatible = "ti,omap-uart";
> +			ti,hwmods = "uart2";
> +		};
> +
> +		uart3: uart at 3 {
> +			compatible = "ti,omap-uart";
> +			ti,hwmods = "uart3";
> +		};
> +
> +		uart4: uart at 4 {
> +			compatible = "ti,omap-uart";
> +			ti,hwmods = "uart4";
> +		};
>  	};
>  };
> diff --git a/arch/arm/boot/dts/omap4-panda.dts b/arch/arm/boot/dts/omap4-panda.dts
> index c702657..aa65449 100644
> --- a/arch/arm/boot/dts/omap4-panda.dts
> +++ b/arch/arm/boot/dts/omap4-panda.dts
> @@ -27,3 +27,20 @@
>  		reg = <0x80000000 0x40000000>; /* 1 GB */
>  	};
>  };
> +
> +&uart1 {
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart2 {
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart3 {
> +	ti,console_hwmod;
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart4 {
> +	clock-frequency = <48000000>;
> +};
> diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch/arm/boot/dts/omap4-sdp.dts
> index 066e28c..524f5bf 100644
> --- a/arch/arm/boot/dts/omap4-sdp.dts
> +++ b/arch/arm/boot/dts/omap4-sdp.dts
> @@ -27,3 +27,20 @@
>  		reg = <0x80000000 0x40000000>; /* 1 GB */
>  	};
>  };
> +
> +&uart1 {
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart2 {
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart3 {
> +	ti,console_hwmod;
> +	clock-frequency = <48000000>;
> +};
> +
> +&uart4 {
> +	clock-frequency = <48000000>;

It doesn't seem that this frequency ever varies and is likely to be
replaced with clock bindings, so maybe just put it in the dtsi files.

Rob

  reply	other threads:[~2011-11-17  1:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 11:02 [PATCH 0/3] OMAP serial device tree support Rajendra Nayak
2011-11-16 11:02 ` [PATCH 1/3] ARM: omap_device: handle first time activation of console device Rajendra Nayak
2011-11-16 14:50   ` Rob Herring
2011-11-16 15:14     ` Cousson, Benoit
2011-11-16 15:41       ` Rob Herring
2011-11-16 18:18         ` Cousson, Benoit
2011-11-17  7:31     ` Rajendra Nayak
2011-11-16 15:01   ` Cousson, Benoit
2011-11-17  7:19     ` Rajendra Nayak
2011-11-17  9:52       ` Cousson, Benoit
2011-11-17 10:16         ` Rajendra Nayak
2011-11-16 11:02 ` [PATCH 2/3] omap-serial: Add minimal device tree support Rajendra Nayak
2011-11-16 14:59   ` Rob Herring
2011-11-17  8:39     ` Rajendra Nayak
2011-11-16 11:02 ` [PATCH 3/3] ARM: omap: pass minimal SoC/board data for UART from dt Rajendra Nayak
2011-11-17  1:04   ` Rob Herring [this message]
2011-11-17  8:42     ` Rajendra Nayak

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=4EC45D9B.5020006@gmail.com \
    --to=robherring2@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).