U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lokesh Vutla <lokeshvutla@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/8] arm: K3: Add support for AM654 SoC definition
Date: Fri, 24 Aug 2018 20:28:17 +0530	[thread overview]
Message-ID: <d641f06b-5fb9-fe8e-758c-bd269de56c0b@ti.com> (raw)
In-Reply-To: <20180824141100.GL26633@bill-the-cat>



On Friday 24 August 2018 07:41 PM, Tom Rini wrote:
> On Tue, Aug 21, 2018 at 08:00:49PM +0530, Lokesh Vutla wrote:
> 
>> The AM654 device is designed for industrial automation and PLC
>> controller class platforms among other applications. Introduce
>> base support for AM654 SoC.
> [snip]
>> +config NON_SECURE_MSRAM_SIZE
>> +	hex "Size of the MCU OC-MSRAM"
>> +	default 0x80000
>> +	help
>> +	  Describes the total size of the MCU MSRAM. This doesn't
>> +	  specify the total size of SPL as ROM can use some part
>> +	  of this RAM. Once ROM gives control to SPL then this
>> +	  complete size can be usable.
>> +
>> +config MAX_DOWNLODABLE_IMAGE_SIZE
>> +	hex "Maximum size of the image"
>> +	default 0x58000
>> +	help
>> +	  Describes the maximum size of the image that ROM can download
>> +	  from any boot media.
>> +
>> +config MCU_SCRATCHPAD_BASE
>> +	hex "Base address of Scratchpad RAM"
>> +	default 0x40280000 if SOC_K3_AM6
>> +	help
>> +	  Describes the base address of MCU Scratchpad RAM.
>> +
>> +config MCU_SCRATCHPAD_SIZE
>> +	hex "Size of Scratchpad RAM"
>> +	default 0x200 if SOC_K3_AM6
>> +	help
>> +	  Describes the size of MCU Scratchpad RAM.
> 
> These are very generic names.  And are these really things that can be
> configured and changed by the user?  MAX_DOWNLODABLE_IMAGE_SIZE is

You are right. These are not configurable by user, but changes from SoC
to SoC within K3 family. Will fix it in v2 by dropping the prompt string.

Thanks and regards,
Lokesh

> something we usually set in CONFIG_SPL_MAX_SIZE but I imagine the
> overall architecture means that perhaps that's not the exact variable
> we're talking about here.
> 

  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 [this message]
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
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=d641f06b-5fb9-fe8e-758c-bd269de56c0b@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