From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Goran Radenovic <goran.radni@gmail.com>, Andrew Lunn <andrew@lunn.ch>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Börge Strümpfel" <boerge.struempfel@gmail.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 4/4] ARM: dts: stm32: add initial support for stm32mp157-ultra-fly-sbc board
Date: Mon, 12 May 2025 11:45:17 +0200 [thread overview]
Message-ID: <66fb604a-ce90-41c4-9ce9-26fa1d81e0d2@foss.st.com> (raw)
In-Reply-To: <35c08d79-1473-4c1e-b605-627c4ff00a92@gmail.com>
Hi Goran
On 5/8/25 15:10, Goran Radenovic wrote:
> Hi Andrew,
>
> thank You once again for helpful hint.
>
> Andrew Lunn wrote:
>>>>> + phy-handle = <&phy1>;
>>>>> +
>>>>> + mdio {
>>>>> + #address-cells = <1>;
>>>>> + #size-cells = <0>;
>>>>> + compatible = "snps,dwmac-mdio";
>>>>> + phy1: ethernet-phy@1 {
>>>>> + reg = <1>;
>>>>> + interrupt-parent = <&gpiod>;
>>>>> + interrupts = <0 IRQ_TYPE_EDGE_FALLING>;
>>>> PHY interrupts are 99% time level, not edge.
>>> That is correct, but I am facing strange behavior, when I set
>>> IRQ_TYPE_LEVEL_LOW.
>>> My board stops booting at:
>>>
>>> [ 2.343233] Waiting for root device /dev/mmcblk0p4...
>>> [ 12.638818] platform 5a006000.usbphyc: deferred probe pending
>>> [ 12.643192] platform 49000000.usb-otg: deferred probe pending
>>> [ 12.649029] platform 48003000.adc: deferred probe pending
>>> [ 12.654277] platform 5800d000.usb: deferred probe pending
>>> [ 12.659744] platform 5800c000.usb: deferred probe pending
>>> [ 12.665089] amba 58005000.mmc: deferred probe pending
>>> [ 12.670239] amba 58007000.mmc: deferred probe pending
>>> [ 12.675185] platform 50025000.vrefbuf: deferred probe pending
>>>
>>> I must investigate this. If You have any idea, You are welcome to
>>> share it.
>> Could be an interrupt storm. The interrupt is not getting cleared
>> because of something missing in the PHY driver, so it just fires again
>> and again.
>
> After a brief investigation, I tend to agree with your assessment that
> the issue lies in the driver—likely the stmmac driver — which is outside
> the scope of my changes.
No, the mdio node is driven by stmmac driver. The issue was maybe more
linked between pinctrl driver / exti driver where the level trigger is
probably not well managed (gpio is level but exti driver manage edge
interrupt). When saw those defering probes, EXTI drivers and pinctrl
drivers were well probed ?
>
> Therefore, I would suggest keeping IRQ_TYPE_EDGE_FALLING for now, or
> alternatively not using a hardware IRQ at all and falling back to
> polling, as done in stm32mp15xx-dkx.dtsi.
>
> Best regards,
> Goran
prev parent reply other threads:[~2025-05-12 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250505115827.29593-1-goran.radni@gmail.com>
2025-05-05 11:58 ` [PATCH v5 1/4] dt-bindings: vendor-prefixes: Add Ultratronik Goran Rađenović
2025-05-05 11:58 ` [PATCH v5 2/4] dt-bindings: arm: stm32: Document Ultratronik's Fly board DT binding Goran Rađenović
2025-05-05 11:58 ` [PATCH v5 3/4] MAINTAINERS: Add entry for ULTRATRONIK BOARD SUPPORT Goran Rađenović
2025-05-05 11:58 ` [PATCH v5 4/4] ARM: dts: stm32: add initial support for stm32mp157-ultra-fly-sbc board Goran Rađenović
2025-05-05 16:26 ` Andrew Lunn
2025-05-07 11:06 ` Goran Radenovic
2025-05-07 12:53 ` Andrew Lunn
2025-05-08 13:10 ` Goran Radenovic
2025-05-08 13:51 ` Andrew Lunn
2025-05-12 9:45 ` Alexandre TORGUE [this message]
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=66fb604a-ce90-41c4-9ce9-26fa1d81e0d2@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=boerge.struempfel@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=goran.radni@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@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
all inboxes | Powered by JetHome®