linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Chen-Yu Tsai <wens@kernel.org>, Jonas Karlman <jonas@kwiboo.se>,
	Diederik de Haas <didi.debian@cknow.org>
Cc: linux-rockchip@lists.infradead.org,
	"Uwe Kleine-König" <ukleinek@debian.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	"Andrew Lunn" <andrew@lunn.ch>
Subject: Re: [PATCH] arm64: dts: rockchip: qnap-ts433: Simplify network PHY connection
Date: Mon, 05 Aug 2024 18:33:52 +0200	[thread overview]
Message-ID: <3723411.CpGBqz00pN@diego> (raw)
In-Reply-To: <1805269.IgJLvJe6uz@bagend>

Am Montag, 4. März 2024, 17:47:22 CEST schrieb Diederik de Haas:
> On Monday, 4 March 2024 16:46:59 CET Jonas Karlman wrote:
> > Sorry for not getting back to you sooner, but yes I would check with
> > phy-mode = "rgmii-id". There is also a possible issue with rk gmac
> > driver in both U-Boot and linux, it always set enable tx/rx delay bit.
> > 
> > Please, try with following in U-Boot:
> 
> No worries :)
> Will try your suggestions soon, but it's probably better to take that 
> discussion somewhere else to not further clutter up this patch/thread.

did you get somewhere with your testing?

Just as a datapoint, I also had a lot of "fun" with the gmac0 on my qnap
ts433 today.

Cable connection was detected but dhcp did not get an IP address.

In the end I realized that the vccio4 supply was 1.8V but the
pmu-io-domains were not enabled, so the soc thought it got 3.3V

After enabling pmu-io-domains [0], I now get networking on that port.


Heiko


[0] https://lore.kernel.org/linux-rockchip/20240805162052.3345768-1-heiko@sntech.de/T/#u





  reply	other threads:[~2024-08-05 16:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  8:46 [PATCH] arm64: dts: rockchip: qnap-ts433: Simplify network PHY connection Uwe Kleine-König
2024-03-04  9:07 ` Heiko Stübner
2024-03-04  9:15   ` Uwe Kleine-König
2024-03-04  9:24     ` Heiko Stübner
2024-03-04 21:03       ` Uwe Kleine-König
2024-03-04 10:07 ` Chen-Yu Tsai
2024-03-04 13:09   ` Andrew Lunn
2024-03-04 15:32     ` Diederik de Haas
2024-03-04 15:46       ` Jonas Karlman
2024-03-04 16:47         ` Diederik de Haas
2024-08-05 16:33           ` Heiko Stübner [this message]
2024-08-05 16:47             ` Diederik de Haas
2024-03-04 15:59       ` Andrew Lunn
2024-03-04 16:43         ` Diederik de Haas
2024-03-04 22:44           ` Uwe Kleine-König
2024-03-06  0:03             ` Diederik de Haas
2024-03-12 18:39               ` Dragan Simic
2024-08-05 16:23 ` Heiko Stuebner

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=3723411.CpGBqz00pN@diego \
    --to=heiko@sntech.de \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=didi.debian@cknow.org \
    --cc=jonas@kwiboo.se \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=ukleinek@debian.org \
    --cc=wens@kernel.org \
    /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).