From: Joshua Milas <josh.milas@gmail.com>
To: Inochi Amaoto <inochiama@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
unicorn_wang@outlook.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
alexander.sverdlin@gmail.com, rabenda.cn@gmail.com,
thomas.bonnefille@bootlin.com, chao.wei@sophgo.com,
liujingqi@lanxincomputing.com, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 2/3] arm64: dts: sophgo: add initial Milk-V Duo S board support
Date: Sat, 11 Oct 2025 15:19:19 -0400 [thread overview]
Message-ID: <aOqtt7BDXxItrs7W@sleek> (raw)
In-Reply-To: <hkdnjyldwr4watvizsju4qcvpvkb3mtt5rathaooembpceyufx@ega5xrqj6v3y>
Hi Inochi,
> Only enable device that can be accessed directly. These devices share
> some pins and only one of them can be used. I suggest enabling devices
> that are accessed by default (which means it is compatible with the
> vendor kernel).
I decompiled the vendor device tree and will match what is in that.
Surprisingly most of these are enabled there. I also tried to check
the pinouts [1] but didnt really get anything out of it.
Link: https://github.com/milkv-duo/duo-files/raw/refs/heads/main/duo-s/hardware/SG2000-PINOUT.xlsx [1]
Thanks,
- Joshua Milas
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Joshua Milas <josh.milas@gmail.com>
To: Inochi Amaoto <inochiama@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
unicorn_wang@outlook.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
alexander.sverdlin@gmail.com, rabenda.cn@gmail.com,
thomas.bonnefille@bootlin.com, chao.wei@sophgo.com,
liujingqi@lanxincomputing.com, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 2/3] arm64: dts: sophgo: add initial Milk-V Duo S board support
Date: Sat, 11 Oct 2025 15:19:19 -0400 [thread overview]
Message-ID: <aOqtt7BDXxItrs7W@sleek> (raw)
In-Reply-To: <hkdnjyldwr4watvizsju4qcvpvkb3mtt5rathaooembpceyufx@ega5xrqj6v3y>
Hi Inochi,
> Only enable device that can be accessed directly. These devices share
> some pins and only one of them can be used. I suggest enabling devices
> that are accessed by default (which means it is compatible with the
> vendor kernel).
I decompiled the vendor device tree and will match what is in that.
Surprisingly most of these are enabled there. I also tried to check
the pinouts [1] but didnt really get anything out of it.
Link: https://github.com/milkv-duo/duo-files/raw/refs/heads/main/duo-s/hardware/SG2000-PINOUT.xlsx [1]
Thanks,
- Joshua Milas
next prev parent reply other threads:[~2025-10-11 19:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 1:48 [PATCH 0/3] Add initial Milk-V Duo S board support Joshua Milas
2025-10-11 1:48 ` Joshua Milas
2025-10-11 1:48 ` [PATCH 1/3] dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles Joshua Milas
2025-10-11 1:48 ` Joshua Milas
2025-10-11 1:50 ` Inochi Amaoto
2025-10-11 1:50 ` Inochi Amaoto
2026-03-21 22:06 ` Joshua Milas
2026-03-21 22:06 ` Joshua Milas
2025-10-11 1:48 ` [PATCH 2/3] arm64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2025-10-11 1:48 ` Joshua Milas
2025-10-11 1:56 ` Inochi Amaoto
2025-10-11 1:56 ` Inochi Amaoto
2025-10-11 19:19 ` Joshua Milas [this message]
2025-10-11 19:19 ` Joshua Milas
2025-10-13 0:43 ` Inochi Amaoto
2025-10-13 0:43 ` Inochi Amaoto
2025-10-26 21:35 ` Joshua Milas
2025-10-26 21:35 ` Joshua Milas
2025-10-26 22:48 ` Michael Opdenacker
2025-10-26 22:48 ` Michael Opdenacker
2025-10-28 23:23 ` Joshua Milas
2025-10-28 23:23 ` Joshua Milas
2025-10-29 0:53 ` Inochi Amaoto
2025-10-29 0:53 ` Inochi Amaoto
2025-10-30 12:50 ` Michael Opdenacker
2025-10-30 12:50 ` Michael Opdenacker
2025-10-11 1:48 ` [PATCH 3/3] riscv64: " Joshua Milas
2025-10-11 1:48 ` Joshua Milas
2025-10-11 1:57 ` Inochi Amaoto
2025-10-11 1:57 ` Inochi Amaoto
2025-10-11 2:16 ` [PATCH 0/3] Add " Chen Wang
2025-10-11 2:16 ` Chen Wang
2025-10-14 3:27 ` Chen Wang
2025-10-14 3:27 ` Chen Wang
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=aOqtt7BDXxItrs7W@sleek \
--to=josh.milas@gmail.com \
--cc=alex@ghiti.fr \
--cc=alexander.sverdlin@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liujingqi@lanxincomputing.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=thomas.bonnefille@bootlin.com \
--cc=unicorn_wang@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.