From: Joshua Milas <josh.milas@gmail.com>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: E Shattow <e@freeshell.de>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
unicorn_wang@outlook.com, inochiama@gmail.com,
rabenda.cn@gmail.com, thomas.bonnefille@bootlin.com,
chao.wei@sophgo.com, devicetree@vger.kernel.org,
sophgo@lists.linux.dev
Subject: Re: [PATCH 2/2] arm64: dts: sophgo: add initial Milk-V Duo S board support
Date: Thu, 2 Oct 2025 21:34:15 -0400 [thread overview]
Message-ID: <aN8oF-44XZooEoVV@sleek> (raw)
In-Reply-To: <9614f7f37f0e76d0dba91b26d83f234e6847818f.camel@gmail.com>
Alexander,
> I wonder why is it necessary to remove "resets" at all, if it's
> exactly the SG2000 SoC. What is the exact problem with them?
When I dont have the 'resets' property removed I don't get any
output, with or without the pinctrl property. I found this out
by comparing the device tree from the released image from milk-v,
it was the only property missing.
- Joshua Milas
next prev parent reply other threads:[~2025-10-03 1:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 17:36 [PATCH 0/2] Add initial Milk-V Duo S board support Joshua Milas
2025-09-27 17:36 ` [PATCH 1/2] dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles Joshua Milas
2025-09-28 4:09 ` E Shattow
2025-09-27 17:36 ` [PATCH 2/2] arm64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2025-09-28 4:09 ` E Shattow
2025-09-28 10:20 ` Alexander Sverdlin
2025-10-03 1:34 ` Joshua Milas [this message]
2025-09-29 23:45 ` Inochi Amaoto
2025-09-29 23:54 ` Inochi Amaoto
2025-09-30 5:03 ` Alexander Sverdlin
2025-10-01 6:46 ` Inochi Amaoto
2025-10-09 1:52 ` Joshua Milas
2025-10-11 6:14 ` Alexander Sverdlin
2025-10-03 1:11 ` Joshua Milas
2025-10-05 3:39 ` Inochi Amaoto
2025-10-09 1:58 ` Joshua Milas
2025-10-05 12:07 ` Inochi Amaoto
2025-09-29 2:14 ` [PATCH 0/2] Add " Rob Herring (Arm)
2025-09-29 6:41 ` 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=aN8oF-44XZooEoVV@sleek \
--to=josh.milas@gmail.com \
--cc=alexander.sverdlin@gmail.com \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=e@freeshell.de \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--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.