From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux@ew.tq-group.com, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: freescale: add initial device tree for TQMa8XxS
Date: Wed, 16 Apr 2025 13:53:52 +0200 [thread overview]
Message-ID: <4975795.GXAFRqVoOG@steina-w> (raw)
In-Reply-To: <aa21556c-8c79-4d03-b6db-3b4cf450fc3a@lunn.ch>
Hi Andrew,
Am Dienstag, 15. April 2025, 17:27:37 CEST schrieb Andrew Lunn:
> > +&fec1 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_fec1>;
> > + phy-mode = "rgmii-id";
> > + phy-handle = <ðphy0>;
> > + fsl,magic-packet;
> > + mac-address = [ 00 00 00 00 00 00 ];
> > +
> > + mdio {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + ethphy0: ethernet-phy@0 {
> > + compatible = "ethernet-phy-ieee802.3-c22";
> > + reg = <0>;
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pinctrl_ethphy0>;
> > + ti,rx-internal-delay = <DP83867_RGMIIDCTL_2_50_NS>;
> > + ti,tx-internal-delay = <DP83867_RGMIIDCTL_2_50_NS>;
> > + ti,fifo-depth = <DP83867_PHYCR_FIFO_DEPTH_4_B_NIB>;
> > + ti,dp83867-rxctrl-strap-quirk;
> > + ti,clk-output-sel = <DP83867_CLK_O_SEL_OFF>;
> > + reset-gpios = <&lsio_gpio3 22 GPIO_ACTIVE_LOW>;
> > + reset-assert-us = <500000>;
> > + reset-deassert-us = <50000>;
> > + enet-phy-lane-no-swap;
> > + interrupt-parent = <&lsio_gpio1>;
> > + interrupts = <30 IRQ_TYPE_EDGE_FALLING>;
>
> EDGE_FALLING is very likely to be wrong. PHYs are generally level
> triggered, not edge.
Thanks for that comment. I checked with my colleagues and it is
indeed level-low. Will fix in v2.
Thanks
Alexander
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2025-04-16 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 13:32 [PATCH 1/2] dt-bindings: arm: add TQMa8XxS boards Alexander Stein
2025-04-15 13:32 ` [PATCH 2/2] arm64: dts: freescale: add initial device tree for TQMa8XxS Alexander Stein
2025-04-15 15:27 ` Andrew Lunn
2025-04-16 11:53 ` Alexander Stein [this message]
2025-04-21 18:48 ` [PATCH 1/2] dt-bindings: arm: add TQMa8XxS boards Rob Herring (Arm)
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=4975795.GXAFRqVoOG@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=geert+renesas@glider.be \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).