U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Zi <me@ziyao.cc>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>, Yao Zi <me@ziyao.cc>
Cc: u-boot@lists.u-boot-project.org, Tom Rini <trini@konsulko.com>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH v5 18/20] doc: arch: Add documentation for LoongArch
Date: Fri, 16 Oct 2026 14:19:32 +0000	[thread overview]
Message-ID: <atIydFGZM--jiRAo@pie> (raw)
In-Reply-To: <1fceeb22-012d-4c41-af64-dbb10be2733b@gmx.de>

On Fri, Oct 16, 2026 at 09:35:16AM +0200, Heinrich Schuchardt wrote:
> On 10/16/26 08:54, Yao Zi wrote:
> > Add a brief introduction to LoongArch architecture, some notes on the
> > implementation, and the toolchain supporting status.
> > 
> > Signed-off-by: Yao Zi <me@ziyao.cc>
> > ---
> > 
> > New patch, no changes since v3
> > ---
> >   doc/arch/index.rst     |  1 +
> >   doc/arch/loongarch.rst | 30 ++++++++++++++++++++++++++++++
> >   2 files changed, 31 insertions(+)
> >   create mode 100644 doc/arch/loongarch.rst

...

> > diff --git a/doc/arch/loongarch.rst b/doc/arch/loongarch.rst
> > new file mode 100644
> > index 000000000000..d744db6a4999
> > --- /dev/null
> > +++ b/doc/arch/loongarch.rst
> > @@ -0,0 +1,30 @@
> > +.. SPDX-License-Identifier: GPL-2.0-or-later
> > +.. Copyright (C) 2026 Yao Zi <me@ziyao.cc>
> > +
> > +LoongArch
> > +=========
> > +
> > +LoongArch is a RISC ISA developed by Loongson Technology. It currently defines
> > +three variants: a reduced 32-bit version (LA32R), a standard 32-bit version
> > +(LA32S) for embedded devices, and a 64-bit version (LA64).
> > +
> > +Notes
> > +-----
> > +
> > +1. Currently U-Boot only runs on LA64 variant with the highest privilege level
> > +   (PLV0).
> > +
> > +2. LA64 is distinguished with 32-bit LoongArch with CONFIG_ARCH_LA64.
> 
> Thank you for the helpful documentation. Just some nits.
> 
> The prepositions should be
> 
> LA64 is distinguished from 32-bit LoongArch by CONFIG_ARCH_LA64.
> 
> Maybe:
> 
> "CONFIG_ARCH_LA64=y selects support for the LA64 instruction set
> architecture."
> 
> > +
> > +3. U-Boot expects hardware-maintained coherency between I-D cache. Cache
> 
> Maybe
> 
> "U-Boot requires hardware-maintained coherency of different levels of
> instruction and data caches."
> 
> > +   topology is probed through CPUCFG; L2 and L3 caches, if present, must be
> 
> Maybe
> 
> "It determines the cache topology by reading CPUCFG registers before
> enabling the caches."

I think it's too detailed and not very helpful to mention the order
between probing cache topology and enabling the cache? i.e., I would
prefer,

> It determines the cache topology by reading CPUCFG registers.

The rest of your suggestions look good to me, thanks.

> Best regards
> 
> Heinrich

Regards,
Yao Zi

> > +   unified or instruction-only. This is true for all commercial LA64 hardware.
> > +   Refer to arch/loongarch/lib/cache.c for further description.

  reply	other threads:[~2026-10-16 14:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  6:54 [PATCH v5 00/20] LoongArch initial support Yao Zi
2026-10-16  6:54 ` [PATCH v5 01/20] lib: fdtdec: Handle multiple memory nodes Yao Zi
2026-10-19 13:20   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 02/20] linux/io.h: Use map_physmem to implement ioremap Yao Zi
2026-10-16  6:54 ` [PATCH v5 03/20] image: Take entry point as an output of setup_booti Yao Zi
2026-10-19 13:20   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 04/20] elf: Define LoongArch bits Yao Zi
2026-10-16  6:54 ` [PATCH v5 05/20] image: Define IH_ARCH_LOONGARCH Yao Zi
2026-10-16  6:54 ` [PATCH v5 06/20] LoongArch: skeleton and headers Yao Zi
2026-10-16  6:54 ` [PATCH v5 07/20] LoongArch: lib: General routines Yao Zi
2026-10-16  6:54 ` [PATCH v5 08/20] LoongArch: CPU assembly routines Yao Zi
2026-10-16  6:54 ` [PATCH v5 09/20] LoongArch: Exception handling Yao Zi
2026-10-16  6:54 ` [PATCH v5 10/20] LoongArch: Boot Image bits Yao Zi
2026-10-16  6:54 ` [PATCH v5 11/20] LoongArch: Generic platform type Yao Zi
2026-10-19 13:15   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 12/20] board_f: Add LoongArch path of mon_len calculation Yao Zi
2026-10-19 13:15   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 13/20] cpu: Add loongarch_cpu driver Yao Zi
2026-10-19 13:15   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 14/20] timer: Add loongarch_timer driver Yao Zi
2026-10-19 13:15   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 15/20] board: emulation: Add qemu-loongarch Yao Zi
2026-10-19 13:15   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 16/20] efi: LoongArch: Define LoongArch bits everywhere Yao Zi
2026-10-19 13:15   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 17/20] efi: LoongArch: Implement everything Yao Zi
2026-10-19 13:16   ` Simon Glass
2026-10-21 19:14     ` Yao Zi
2026-10-16  6:54 ` [PATCH v5 18/20] doc: arch: Add documentation for LoongArch Yao Zi
2026-10-16  7:35   ` Heinrich Schuchardt
2026-10-16 14:19     ` Yao Zi [this message]
2026-10-19 13:16   ` Simon Glass
2026-10-16  6:54 ` [PATCH v5 19/20] MAINTAINERS: Add entry " Yao Zi
2026-10-19 13:16   ` Simon Glass
2026-10-16  6:55 ` [PATCH v5 20/20] CI: Wire up qemu-loongarch64 Yao Zi
2026-10-19 13:16   ` Simon Glass

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=atIydFGZM--jiRAo@pie \
    --to=me@ziyao.cc \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=xypron.glpk@gmx.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