linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	Imre Kaloz <kaloz@openwrt.org>,
	Krzysztof Halasa <khalasa@piap.pl>,
	phj@phj.hu
Subject: Re: [PATCH] ARM: dts: ixp4xx: Add devicetree for Linksys WRV54G
Date: Thu, 29 Jul 2021 17:33:26 +0200	[thread overview]
Message-ID: <YQLKRn0RPgBv1sw7@lunn.ch> (raw)
In-Reply-To: <20210729082658.2815884-1-linus.walleij@linaro.org>

> +	/* This set-up comes from an OpenWrt patch */
> +	spi {
> +		compatible = "spi-gpio";
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +
> +		sck-gpios = <&gpio0 7 GPIO_ACTIVE_HIGH>;
> +		miso-gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
> +		mosi-gpios = <&gpio0 6 GPIO_ACTIVE_HIGH>;
> +		cs-gpios = <&gpio0 5 GPIO_ACTIVE_LOW>;
> +		num-chipselects = <1>;
> +
> +		switch@0 {
> +			compatible = "micrel,ks8995";

Hi Linus

This does not exist in mainline. And when it does, i guess it will be
called microchip,ksz8995. See microchip,ksz.yaml. It is also missing
all the ethernet-ports nodes. Maybe leave this out until the driver
gets ported?

> +		/*
> +		 * EthB - connected to the KS8995 switch ports 1-4
> +		 * FIXME: the boardfile defines .phy_mask = 0x1e for this port to enable output to
> +		 * all four switch ports, also using an out of tree multiphy patch.
> +		 * Do we need a new binding and property for this?
> +		 */

This sounds like an issue with the KS8995 driver in OpenWRT.

> +		ethernet@c8009000 {
> +			status = "ok";
> +			queue-rx = <&qmgr 3>;
> +			queue-txready = <&qmgr 20>;
> +			phy-mode = "rgmii";
> +			phy-handle = <&phy4>;

It looks like phy4 is a switch PHY. It is not actually connected to
this MAC? So this is wrong for mainline.

> +
> +			mdio {
> +				#address-cells = <1>;
> +				#size-cells = <0>;
> +
> +				/* Should be ports 1-4 on the KS8995 switch */
> +				phy4: ethernet-phy@4 {
> +					reg = <4>;
> +				};
> +
> +				/* Should be port 5 on the KS8995 switch */
> +				phy5: ethernet-phy@5 {
> +					reg = <5>;
> +				};
> +			};
> +		};
> +
> +		/* EthC - connected to KS8995 switch port 5 */
> +		ethernet@c800a000 {
> +			status = "ok";
> +			queue-rx = <&qmgr 4>;
> +			queue-txready = <&qmgr 21>;
> +			phy-mode = "rgmii";
> +			phy-handle = <&phy5>;

And i doubt this is correct. Unless there are back to back PHYs?

I would suggest you leave out all the switch related properties until
the switch driver is available.

    Andrew

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-07-29 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  8:26 [PATCH] ARM: dts: ixp4xx: Add devicetree for Linksys WRV54G Linus Walleij
2021-07-29 15:33 ` Andrew Lunn [this message]
2021-07-30 12:15   ` Linus Walleij
2021-07-30 23:01     ` Andrew Lunn
2021-07-30 12:33   ` Linus Walleij

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=YQLKRn0RPgBv1sw7@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=kaloz@openwrt.org \
    --cc=khalasa@piap.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=phj@phj.hu \
    /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;
as well as URLs for NNTP newsgroup(s).