From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Lukasz Majewski <lukma@denx.de>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: devicetree@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: at91: ksz9477_evb: Add tx-internal-delay-ps property for port5
Date: Thu, 24 Aug 2023 13:00:25 +0300 [thread overview]
Message-ID: <e7136b58-f48b-ff9a-8831-57a905bc0465@tuxon.dev> (raw)
In-Reply-To: <20230824111702.1a034801@wsk>
Hi, Lukasz,
On 8/24/23 12:17, Lukasz Majewski wrote:
> Dear Community,
>
>> Without this change the KSZ9477 Evaluation board's Linux (v6.5-rc1)
>> shows following device warning:
>>
>> 'ksz-switch spi1.0: Port 5 interpreting RGMII delay settings based on
>> "phy-mode" property, please update device tree to specify
>> "rx-internal-delay-ps" and "tx-internal-delay-ps"'
>>
>> This is not critical, as KSZ driver by itself assigns default value of
>> tx delay to 2000 ps (as 'rgmii-txid' is set as PHY mode).
>>
>> However, to avoid extra warnings in logs - the missing
>> 'tx-internal-delay-ps' has been specified with the default value of
>> 2000 ps.
>>
>
> Gentle ping on this patch.
>
> Claudiu, could you pick it as well?
It's already in arm-soc:
https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/log/arch/arm/boot/dts/microchip?h=for-next
prev parent reply other threads:[~2023-08-24 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 8:06 [PATCH] ARM: dts: at91: ksz9477_evb: Add tx-internal-delay-ps property for port5 Lukasz Majewski
2023-08-02 4:50 ` claudiu beznea
2023-08-24 9:17 ` Lukasz Majewski
2023-08-24 10:00 ` claudiu beznea [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=e7136b58-f48b-ff9a-8831-57a905bc0465@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--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-kernel@vger.kernel.org \
--cc=lukma@denx.de \
--cc=robh+dt@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).