From: Nikita Shubin <nikita.shubin@maquefel.me>
Cc: linux@yadro.com, Nikita Shubin <n.shubin@yadro.com>,
Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Simon Glass <sjg@chromium.org>, Bin Meng <bmeng.cn@gmail.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Sergei Miroshnichenko <s.miroshnichenko@yadro.com>,
Alexandru Gagniuc <mr.nuke.me@gmail.com>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Andrew Davis <afd@ti.com>,
u-boot@lists.denx.de
Subject: [RFC PATCH 0/1] spl: introduce SPL_XIP to config
Date: Thu, 11 Aug 2022 12:37:05 +0300 [thread overview]
Message-ID: <20220811093706.3772-1-nikita.shubin@maquefel.me> (raw)
From: Nikita Shubin <n.shubin@yadro.com>
U-Boot and SPL don't necessary share the same location, so we might end
with XIP SPL and U-Boot in "normal" memory.
Actually, it seems that we need only hart_lottery and available_harts_lock to
function like a R/W memory.
May be we should introduce a new section solely for this two locks copy and
initialize it somewhere befor hart lottery or place config variable with
desired location for locks, but we still end up with a need for a
"master" hart.
Does anyone have some thoughts about this ?
Nikita Shubin (1):
spl: introduce SPL_XIP to config
arch/riscv/cpu/cpu.c | 2 +-
arch/riscv/cpu/start.S | 4 ++--
arch/riscv/include/asm/global_data.h | 2 +-
arch/riscv/lib/asm-offsets.c | 2 +-
arch/riscv/lib/smp.c | 2 +-
common/spl/Kconfig | 5 +++++
include/configs/scr7_vcu118.h | 2 ++
7 files changed, 13 insertions(+), 6 deletions(-)
--
2.35.1
next reply other threads:[~2022-08-11 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 9:37 Nikita Shubin [this message]
2022-08-11 9:37 ` [RFC PATCH 1/1] spl: introduce SPL_XIP to config Nikita Shubin
2022-08-13 4:35 ` Sean Anderson
2022-08-15 7:27 ` Nikita Shubin
2022-08-23 4:25 ` Sean Anderson
2022-08-26 8:44 ` [PATCH] " Nikita Shubin
2022-08-26 14:10 ` Sean Anderson
2022-08-31 7:25 ` [PATCH v2] " Nikita Shubin
[not found] ` <HK0PR03MB2994C85219E6217F7F9F4A05C17A9@HK0PR03MB2994.apcprd03.prod.outlook.com>
2022-09-02 7:25 ` Rick Chen
2022-09-02 8:42 ` Nikita Shubin
2022-09-02 8:47 ` [PATCH v3] " Nikita Shubin
[not found] ` <HK0PR03MB29942A55774ED60C5568E72CC17F9@HK0PR03MB2994.apcprd03.prod.outlook.com>
2022-09-08 0:45 ` Rick Chen
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=20220811093706.3772-1-nikita.shubin@maquefel.me \
--to=nikita.shubin@maquefel.me \
--cc=afd@ti.com \
--cc=alpernebiyasak@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=linux@yadro.com \
--cc=mr.nuke.me@gmail.com \
--cc=n.shubin@yadro.com \
--cc=rick@andestech.com \
--cc=s.miroshnichenko@yadro.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=ycliang@andestech.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).