linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: "Derald D. Woods" <woods.technical@gmail.com>
Cc: linux-omap@vger.kernel.org, tony@atomide.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information
Date: Tue, 12 Dec 2017 07:39:30 +0100	[thread overview]
Message-ID: <20171212063930.GA2791@lenoch> (raw)
In-Reply-To: <20171212041213.27436-1-woods.technical@gmail.com>

On Mon, Dec 11, 2017 at 10:12:13PM -0600, Derald D. Woods wrote:
> The partition information was omitted during the conversion to OMAP3430
> specific data.

That could be intentional...

> The data added by this commit is consistent with current U-Boot default
> definitions.

What about passing U-Boot partitions information to kernel instead?

> Fixes: 62fe1d337461 ("ARM: dts: omap3-evm: Add OMAP3530 specific device
> tree processor data")
> 
> Signed-off-by: Derald D. Woods <woods.technical@gmail.com>
> ---
>  arch/arm/boot/dts/omap3-evm.dts | 25 +++++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/omap3-evm.dts b/arch/arm/boot/dts/omap3-evm.dts
> index 21a3b88aef0c..1220deb47aae 100644
> --- a/arch/arm/boot/dts/omap3-evm.dts
> +++ b/arch/arm/boot/dts/omap3-evm.dts
> @@ -85,5 +85,30 @@
>  
>  		#address-cells = <1>;
>  		#size-cells = <1>;
> +
> +		partition@0 {
> +			label = "spl";
> +			reg = <0 0x80000>;
> +		};
> +		partition@80000 {
> +			label = "u-boot";
> +			reg = <0x80000 0x1c0000>;
> +		};
> +		partition@240000 {
> +			label = "dtb";
> +			reg = <0x240000 0x20000>;
> +		};
> +		partition@260000 {
> +			label = "u-boot-env";
> +			reg = <0x260000 0x20000>;
> +		};
> +		partition@280000 {
> +			label = "kernel";
> +			reg = <0x280000 0x600000>;
> +		};
> +		partition@880000 {
> +			label = "rootfs";
> +			reg = <0x880000 0>;
> +		};
>  	};
>  };
> -- 
> 2.15.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-12-12  6:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12  4:12 [PATCH] ARM: dts: omap3-evm: Fix missing NAND partition information Derald D. Woods
2017-12-12  6:39 ` Ladislav Michl [this message]
2017-12-12 16:31   ` Derald D. Woods
2017-12-12 16:55     ` Tony Lindgren
2017-12-12 17:50       ` Ladislav Michl
2017-12-12 18:08         ` Derald D. Woods
2017-12-12 18:15           ` Tony Lindgren
2017-12-12 18:24             ` Derald D. Woods
2017-12-12 18:40               ` Ladislav Michl
     [not found]                 ` <CAHCN7xKn2-6NVhy6MegJgEZrF3=DFigvHW6xf0Gb2BFRTJMDNw@mail.gmail.com>
2017-12-13 13:44                   ` Derald D. Woods
2017-12-13 15:05                     ` Ladislav Michl
2017-12-13 15:37                       ` Derald D. Woods
2017-12-12 17:03     ` Ladislav Michl

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=20171212063930.GA2791@lenoch \
    --to=ladis@linux-mips.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=woods.technical@gmail.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).