From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gregoire Gentil <gregoire@gentil.com>
Date: Wed, 01 Oct 2014 12:13:50 -0700
Subject: [U-Boot] Boot reason in SPL for OMAP4
In-Reply-To: <20141001173456.GZ25506@bill-the-cat>
References: <542AE7B0.6000300@gentil.com> <20141001173456.GZ25506@bill-the-cat>
Message-ID: <542C526E.2010705@gentil.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de



On 10/01/2014 10:34 AM, Tom Rini wrote:
> On Tue, Sep 30, 2014 at 10:26:08AM -0700, Gregoire Gentil wrote:
>
>> Hello,
>>
>> In TI x-loader, the boot reason is copied to a scratchpad 0x4A326000
>> as shown here:
>> https://gitorious.org/x-loader/x-loader/source/HEAD:cpu/omap4/start.S#L102
>>
>> How can I access the boot reason in u-boot or in the SPL?
>
> spl_boot_mode() and spl_boot_device().
>
Thank you. Yes, I found the calls. My point is that I need the 
boot_device after SPL and it's not transmitted down the chain. Doing the 
following reestablishes what the legacy x-loader was doing:

*(volatile unsigned int *)(0x4A326000) = spl_boot_device();

I think that it's safe as the SRAM is not used after SPL,

Gr?goire