linux-rockchip.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: "Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Andrew Lunn" <andrew@lunn.ch>,
	"Uwe Kleine-König" <ukleinek@debian.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: qnap-ts433: Simplify network PHY connection
Date: Mon, 04 Mar 2024 10:24:43 +0100	[thread overview]
Message-ID: <3246455.0WQXIW03uk@diego> (raw)
In-Reply-To: <0f7d2882-aa4b-424e-a999-45f2e18fc7f0@debian.org>

Hi Uwe,

Am Montag, 4. März 2024, 10:15:57 CET schrieb Uwe Kleine-König:
> On 04.03.24 10:07, Heiko Stübner wrote:
> > Am Montag, 4. März 2024, 09:46:11 CET schrieb Uwe Kleine-König:
> >> While it requires to have the right phy driver loaded (i.e. motorcomm)
> >> to make the phy asserting the right delays, this is generally the
> >> preferred way to define the MAC <-> PHY connection.
> >>
> >> Signed-off-by: Uwe Kleine-König <ukleinek@debian.org>
> >> ---
> >> Hello,
> >>
> >> Andrew already pointed out when I posted the patch introducing the gmac0 node
> >> that rgmii-id would be the preferred way to setup things. Back then this didn't
> >> happen because this change broke reception of network packets. However this
> >> only happend because I didn't have the right phy driver loaded.
> > 
> > trying to understand how the (not) loaded module fits into this :-)
> > The mdio-bus is supposed to probe the phy and load the appropriate module.
> > 
> >  From your description it sounds like the correct phy module needs to be
> > actually loaded? Or was that meant to be a "requires to have the right phy
> > driver compiled" instead?
> 
> The latter. i.e. with MOTORCOMM_PHY=n it's broken, but works fine with 
> MOTORCOMM_PHY=y or =m.

ah great, then it's really fine. If it's ok with you I'll change the "loaded"
to "available" then (for compiled in or as module)


Heiko



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2024-03-04  9:25 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 [this message]
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
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=3246455.0WQXIW03uk@diego \
    --to=heiko@sntech.de \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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 \
    /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).