From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Chanh Nguyen <chanh@os.amperecomputing.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Joel Stanley <joel@jms.id.au>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
Thang Nguyen <thang@os.amperecomputing.com>,
Quan Nguyen <quan@os.amperecomputing.com>,
Khanh Pham <khpham@amperecomputing.com>
Subject: Re: [PATCH] ARM: dts: aspeed: Add device tree for Ampere's Mt. Jefferson BMC
Date: Fri, 18 Oct 2024 15:04:40 +1030 [thread overview]
Message-ID: <d514fd066353c529052e59c564d1d15f91b6a8b5.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20241014105031.1963079-1-chanh@os.amperecomputing.com>
Hi Chanh,
On Mon, 2024-10-14 at 10:50 +0000, Chanh Nguyen wrote:
>
> +&mac3 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_rmii4_default>;
> + clock-names = "MACCLK", "RCLK";
Should this be overriding `clocks` also? There's only one clock
specified in the dtsi.
Andrew
> + use-ncsi;
> +};
next prev parent reply other threads:[~2024-10-18 4:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 10:50 [PATCH] ARM: dts: aspeed: Add device tree for Ampere's Mt. Jefferson BMC Chanh Nguyen
2024-10-14 10:54 ` Chanh Nguyen
2024-10-14 11:58 ` Krzysztof Kozlowski
2024-10-14 15:02 ` Chanh Nguyen
2024-10-14 14:05 ` Rob Herring (Arm)
2024-10-15 0:44 ` Andrew Jeffery
2024-10-15 6:39 ` Chanh Nguyen
2024-10-16 5:07 ` Andrew Jeffery
2024-10-16 10:26 ` Chanh Nguyen
2024-10-17 0:08 ` Andrew Jeffery
2024-10-17 10:02 ` Chanh Nguyen
2024-10-18 4:35 ` Andrew Jeffery
2024-10-18 4:34 ` Andrew Jeffery [this message]
2024-10-18 10:08 ` Chanh Nguyen
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=d514fd066353c529052e59c564d1d15f91b6a8b5.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=chanh@os.amperecomputing.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=khpham@amperecomputing.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=robh+dt@kernel.org \
--cc=thang@os.amperecomputing.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