devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Wang <unicornxw@gmail.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	 Conor Dooley <conor@kernel.org>,
	"xiaoguang.xing" <xiaoguang.xing@sophgo.com>,
	jszhang@kernel.org,  Inochi Amaoto <inochiama@outlook.com>,
	devicetree@vger.kernel.org,  linux-kernel@vger.kernel.org
Cc: Chen Wang <unicornxw@gmail.com>
Subject: Question about writing binding files for numa
Date: Tue, 19 Sep 2023 13:33:16 +0800	[thread overview]
Message-ID: <CAHAQgRC5-tSnUZXHxTeVDhYK1m0XCzXho097bV2Awj-6XJ-UFA@mail.gmail.com> (raw)

Hi, I am working on writing dts for a new SOC - SG2042, you can see
the changes on https://github.com/unicornx/linux-riscv/commit/ee862fc4ebeade32bff00ad014d6b0513c0942a7.
This hardware uses a NUMA architecture,  so a "distance-map" node is
added and several "numa-node-id" are added for cpu/memory. The problem
is I find there is no YAML binding for numa, I only find
"Documentation/devicetree/bindings/numa.txt". To pass dtb check I want
to convert the txt to yaml file.

My question is: how to handle the "numa-node-id" which is listed in
the numa.txt file. To my understanding, due to cpu/memory node need to
contain this property. I should find some binding files for cpu/memory
and add "numa-node-id" for cpu/memory.
For "cpu", I find a
"Documentation/devicetree/bindings/riscv/cpus.yaml", where I think I
can add a property of   "numa-node-id" to. Note the SG2042 is a RISC-V
chip.
But for "memory", where should I add  "numa-node-id" definition to?

Regards,

Chen Wang

             reply	other threads:[~2023-09-19  5:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  5:33 Chen Wang [this message]
2023-09-20  9:59 ` Question about writing binding files for numa Conor Dooley

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=CAHAQgRC5-tSnUZXHxTeVDhYK1m0XCzXho097bV2Awj-6XJ-UFA@mail.gmail.com \
    --to=unicornxw@gmail.com \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=inochiama@outlook.com \
    --cc=jszhang@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=xiaoguang.xing@sophgo.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).