[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210813034016.GA21895@taoren-ubuntu-R90MNF91>
Date: Thu, 12 Aug 2021 20:40:17 -0700
From: Tao Ren <rentao.bupt@...il.com>
To: Joel Stanley <joel@....id.au>
Cc: Rob Herring <robh+dt@...nel.org>, Andrew Jeffery <andrew@...id.au>,
devicetree <devicetree@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-aspeed <linux-aspeed@...ts.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
OpenBMC Maillist <openbmc@...ts.ozlabs.org>,
Tao Ren <taoren@...com>
Subject: Re: [PATCH v2 4/6] ARM: dts: aspeed: Add Facebook Cloudripper
(AST2600) BMC
On Fri, Aug 13, 2021 at 01:29:17AM +0000, Joel Stanley wrote:
> On Thu, 5 Aug 2021 at 22:28, <rentao.bupt@...il.com> wrote:
> > +&mdio1 {
> > + status = "okay";
>
> You're enabling this but it looks like it's unused?
Thanks Joel for the careful review. The MDIO controller is not paired
with BMC MAC; instead, it's connected to the MDC/MDIO interface of the
on-board switch (whose ports are connected to BMC, Host and front panel
management port).
In other word, the MDIO controller is used, but we do need some user
space scripts to control the controller. What's your suggestion? For
example, should I add some comments to explain the purpose?
Cheers,
Tao
>
> > +};
> > +
> > +&mdio3 {
> > + status = "okay";
> > +
> > + ethphy1: ethernet-phy@13 {
> > + compatible = "ethernet-phy-ieee802.3-c22";
> > + reg = <0x0d>;
> > + };
> > +};
> > +
> > +&mac3 {
> > + status = "okay";
> > + phy-mode = "rgmii";
> > + phy-handle = <ðphy1>;
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_rgmii4_default>;
> > +};
Powered by blists - more mailing lists