From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/8] arm: K3: am654: Add support for boot device detection
Date: Fri, 24 Aug 2018 20:28:58 +0530 [thread overview]
Message-ID: <236157fe-90a3-7fb7-de6c-13d21403958f@ti.com> (raw)
In-Reply-To: <20180824141105.GM26633@bill-the-cat>
On Friday 24 August 2018 07:41 PM, Tom Rini wrote:
> On Tue, Aug 21, 2018 at 08:00:51PM +0530, Lokesh Vutla wrote:
>
>> AM654 allows for booting from primary or backup boot media.
>> Both media can be chosen individually based on switch settings.
>> ROM looks for a valid image in primary boot media, if not found
>> then looks in backup boot media. In order to pass this boot media
>> information to boot loader, ROM stores a value at a particular
>> address. Add support for reading this information and determining
>> the boot media correctly.
> [snip]
>> diff --git a/arch/arm/mach-k3/Kconfig b/arch/arm/mach-k3/Kconfig
>> index c532fbd061..117e5b4e4a 100644
>> --- a/arch/arm/mach-k3/Kconfig
>> +++ b/arch/arm/mach-k3/Kconfig
>> @@ -40,4 +40,11 @@ config MCU_SCRATCHPAD_SIZE
>> help
>> Describes the size of MCU Scratchpad RAM.
>>
>> +config BOOT_PARAM_TABLE_INDEX
>> + hex "Address of Array Index to be used within BOOT_PARAM_TABLE"
>> + default 0x41c7fbfc if SOC_K3_AM6
>> + help
>> + Address at which ROM stores the value which determines if SPL
>> + is booted up by primary boot media or secondary boot media.
>> +
>
> I'm not sure this belongs in Kconfig. This isn't configurable really is
> it?
Agreed. Will drop the prompt string in v2.
>
>> +static u32 __get_backup_bootmedia(u32 devstat)
>> {
>> + u32 bkup_boot = (devstat & CTRLMMR_MAIN_DEVSTAT_BKUP_BOOTMODE_MASK) >>
>> + CTRLMMR_MAIN_DEVSTAT_BKUP_BOOTMODE_SHIFT;
>> +
>> + switch (bkup_boot) {
>> +#define __BKUP_BOOT_DEVICE(n) \
>> + case BACKUP_BOOT_DEVICE_##n: \
>> + return BOOT_DEVICE_##n;
>
> I really don't like defining the macro in the function like this. And
> in terms of style, I think I'd rather see it spelled out with
> case/return as is normally done.
Sure. Will fix it in v2.
Thanks and regards,
Lokesh
>
next prev parent reply other threads:[~2018-08-24 14:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 14:30 [U-Boot] [PATCH 0/8] [1/3] Initial support Texas Instrument's AM654 Platform Lokesh Vutla
2018-08-21 14:30 ` [U-Boot] [PATCH 1/8] arm: K3: Add initial support for TI's K3 generation of SoCs Lokesh Vutla
2018-08-24 14:10 ` Tom Rini
2018-08-24 14:51 ` Lokesh Vutla
2018-08-24 14:55 ` Tom Rini
2018-08-24 15:14 ` Lokesh Vutla
2018-08-24 15:21 ` Tom Rini
2018-08-21 14:30 ` [U-Boot] [PATCH 2/8] arm: K3: Add support for AM654 SoC definition Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-24 14:58 ` Lokesh Vutla
2018-08-24 15:01 ` Tom Rini
2018-08-21 14:30 ` [U-Boot] [PATCH 3/8] arm: K3: Update _start instruction Lokesh Vutla
2018-08-21 14:30 ` [U-Boot] [PATCH 4/8] arm: K3: am654: Add support for boot device detection Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-24 14:58 ` Lokesh Vutla [this message]
2018-08-21 14:30 ` [U-Boot] [PATCH 5/8] arm: K3: am654: Unlock control module registers during init Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-21 14:30 ` [U-Boot] [PATCH 6/8] armv8: K3: am654: Add custom MMU support Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-21 14:30 ` [U-Boot] [PATCH 7/8] armv8: K3: am654: Introduce FIT generator script Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-24 14:59 ` Lokesh Vutla
2018-08-21 14:30 ` [U-Boot] [PATCH 8/8] armv8: K3: am654: Add support for generating build targets Lokesh Vutla
2018-08-24 14:11 ` Tom Rini
2018-08-26 6:11 ` [U-Boot] [PATCH 0/8] [1/3] Initial support Texas Instrument's AM654 Platform Alexander Graf
2018-08-27 9:31 ` Lokesh Vutla
2018-08-27 9:52 ` Alexander Graf
2018-08-27 10:07 ` Lokesh Vutla
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=236157fe-90a3-7fb7-de6c-13d21403958f@ti.com \
--to=lokeshvutla@ti.com \
--cc=u-boot@lists.denx.de \
/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