From: Andrew Lunn <andrew@lunn.ch>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"sebastian.hesselbarth@gmail.com"
<sebastian.hesselbarth@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"kostap@marvell.com" <kostap@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm/arm64: dts: Add MV88E6393X to CN9130-CRB device tree
Date: Sun, 10 Oct 2021 17:21:17 +0200 [thread overview]
Message-ID: <YWME7f31MzaTvL8N@lunn.ch> (raw)
In-Reply-To: <YWL8laRaWwordXdE@lunn.ch>
> Given that this is a marvell device, you might also need some comphy
> configuration in the MAC node:
>
> phy-names = "comphy";
> phys = <&cps_comphy5 0>;
Humm, actually, forget that, this is a switch, not a SoC.
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"sebastian.hesselbarth@gmail.com"
<sebastian.hesselbarth@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"kostap@marvell.com" <kostap@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm/arm64: dts: Add MV88E6393X to CN9130-CRB device tree
Date: Sun, 10 Oct 2021 17:21:17 +0200 [thread overview]
Message-ID: <YWME7f31MzaTvL8N@lunn.ch> (raw)
In-Reply-To: <YWL8laRaWwordXdE@lunn.ch>
> Given that this is a marvell device, you might also need some comphy
> configuration in the MAC node:
>
> phy-names = "comphy";
> phys = <&cps_comphy5 0>;
Humm, actually, forget that, this is a switch, not a SoC.
Andrew
next prev parent reply other threads:[~2021-10-10 15:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 23:06 [PATCH 0/2] arm/arm64: dts: Enable more network hardware Chris Packham
2021-10-07 23:06 ` Chris Packham
2021-10-07 23:06 ` [PATCH 1/2] arm/arm64: dts: Enable 2.5G Ethernet port on CN9130-CRB Chris Packham
2021-10-07 23:06 ` Chris Packham
2021-10-07 23:45 ` Andrew Lunn
2021-10-07 23:45 ` Andrew Lunn
2021-10-13 14:52 ` Gregory CLEMENT
2021-10-13 14:52 ` Gregory CLEMENT
2021-10-17 22:15 ` Chris Packham
2021-10-17 22:15 ` Chris Packham
2021-11-09 1:00 ` Chris Packham
2021-11-09 1:00 ` Chris Packham
2021-10-07 23:06 ` [PATCH 2/2] arm/arm64: dts: Add MV88E6393X to CN9130-CRB device tree Chris Packham
2021-10-07 23:06 ` Chris Packham
2021-10-07 23:51 ` Andrew Lunn
2021-10-07 23:51 ` Andrew Lunn
2021-10-08 0:09 ` Chris Packham
2021-10-08 0:09 ` Chris Packham
2021-10-10 14:45 ` Andrew Lunn
2021-10-10 14:45 ` Andrew Lunn
2021-10-10 15:21 ` Andrew Lunn [this message]
2021-10-10 15:21 ` Andrew Lunn
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=YWME7f31MzaTvL8N@lunn.ch \
--to=andrew@lunn.ch \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kostap@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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.