Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Binbin Zhou <zhoubinbin@loongson.cn>
Cc: Binbin Zhou <zhoubb.aaron@gmail.com>,
	Huacai Chen <chenhuacai@loongson.cn>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, Huacai Chen <chenhuacai@kernel.org>,
	Xuerui Wang <kernel@xen0n.name>,
	loongarch@lists.linux.dev, Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Hongliang Wang <wanghongliang@loongson.cn>
Subject: Re: [PATCH v6 0/7] LoongArch: Add built-in dtb support
Date: Fri, 22 Dec 2023 15:38:59 +0000	[thread overview]
Message-ID: <20231222-support-relieve-5d8f25292b40@spud> (raw)
In-Reply-To: <cover.1703229766.git.zhoubinbin@loongson.cn>

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

Hey Binbin,

On Fri, Dec 22, 2023 at 04:00:43PM +0800, Binbin Zhou wrote:
> Hi all:
> 
> This patchset introduces LoongArch's built-in dtb support.
> 
> During the upstream progress of those DT-based drivers, DT properties
> are changed a lot so very different from those in existing bootloaders.
> It is inevitably that some existing systems do not provide a standard,
> canonical device tree to the kernel at boot time. So let's provide a
> device tree table in the kernel, keyed by the dts filename, containing
> the relevant DTBs.
> 
> We can use the built-in dts files as references. Each SoC has only one
> built-in dts file which describes all possible device information of
> that SoC, so the dts files are good examples during development.
> 
> And as a reference, our built-in dts file only enables the most basic
> bootable combinations (so it is generic enough), acts as an alternative
> in case the dts in the bootloader is unexpected.
> 
> In the past while, we resolved the DTC_CHK warning for the v4 patchset,
> and the relevant patchset has either been applied or had the
> Reviewed-by tag added. 

I notice you dropped the topology information from all patches in the
series, not only the 2k0500 patch that only has one CPU. I didn't see a
response to my comments the kernel being able to assemble the topology
based on the second level caches using the generic topology code for the
systems that have more than one cpu. With the cpu-map information
dropped, do the multi-cpu systems have their topologies assembled
correctly by the kernel?
You mentioned that there is an instruction that allows you to get
information about i and d caches etc, so adding them to the DT is not
required, but does it also cover the next level caches?
The program that I am familiar with for displaying this information
is hwloc: https://github.com/open-mpi/hwloc

Cheers,
Conor.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2023-12-22 15:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22  8:00 [PATCH v6 0/7] LoongArch: Add built-in dtb support Binbin Zhou
2023-12-22  8:00 ` [PATCH v6 1/7] dt-bindings: loongarch: Add CPU bindings for LoongArch Binbin Zhou
2023-12-22  8:00 ` [PATCH v6 2/7] dt-bindings: loongarch: Add Loongson SoC boards compatibles Binbin Zhou
2023-12-22  8:00 ` [PATCH v6 3/7] LoongArch: Allow device trees to be built into the kernel Binbin Zhou
2023-12-22  8:01 ` [PATCH v6 4/7] LoongArch: dts: DeviceTree for Loongson-2K0500 Binbin Zhou
2023-12-22  8:01 ` [PATCH v6 5/7] LoongArch: dts: DeviceTree for Loongson-2K1000 Binbin Zhou
2023-12-22  8:01 ` [PATCH v6 6/7] LoongArch: dts: DeviceTree for Loongson-2K2000 Binbin Zhou
2023-12-22  8:01 ` [PATCH v6 7/7] LoongArch: Parsing CPU-related information from DTS Binbin Zhou
2023-12-22 15:38 ` Conor Dooley [this message]
2023-12-27  6:04   ` [PATCH v6 0/7] LoongArch: Add built-in dtb support Binbin Zhou
2023-12-28 14:09     ` Conor Dooley
2023-12-29 15:10       ` Huacai Chen
2024-01-09  9:57         ` Huacai Chen
2024-01-09 11:14           ` Krzysztof Kozlowski
2024-01-09 12:13             ` Huacai Chen
2024-01-09 13:33               ` Krzysztof Kozlowski
2024-01-09 15:02                 ` Huacai Chen
2024-01-09 15:13                   ` Krzysztof Kozlowski
2024-01-09 15:25                     ` Huacai 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=20231222-support-relieve-5d8f25292b40@spud \
    --to=conor@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=loongarch@lists.linux.dev \
    --cc=robh+dt@kernel.org \
    --cc=wanghongliang@loongson.cn \
    --cc=zhoubb.aaron@gmail.com \
    --cc=zhoubinbin@loongson.cn \
    /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