From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Marek Vasut <marex@denx.de>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] dt-bindings: net: dsa: microchip: add reset timing properties
Date: Sun, 4 Oct 2026 09:27:04 +0200 [thread overview]
Message-ID: <20261004-transparent-cuscus-of-honor-8ccbb4@quoll> (raw)
In-Reply-To: <20261002135542.359756-2-giometti@enneenne.com>
On Fri, Oct 02, 2026 at 03:55:41PM +0200, Rodolfo Giometti wrote:
> How long a KSZ switch needs before it answers on its management bus
> after the reset line is released depends on the board it sits on, and a
> board that needs longer than the driver waits has no way to say so.
Not completely. This is implied by compatible. Individual phys/mdios
have their own delays but not the entire device.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-04 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 13:55 [PATCH net-next 0/2] net: dsa: microchip: let the board state its reset timing Rodolfo Giometti
2026-10-02 13:55 ` [PATCH net-next 1/2] dt-bindings: net: dsa: microchip: add reset timing properties Rodolfo Giometti
2026-10-04 7:27 ` Krzysztof Kozlowski [this message]
2026-10-05 8:35 ` Rodolfo Giometti
2026-10-02 13:55 ` [PATCH net-next 2/2] net: dsa: microchip: take the reset timings from the device tree Rodolfo Giometti
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=20261004-transparent-cuscus-of-honor-8ccbb4@quoll \
--to=krzk@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@kernel.org \
--cc=giometti@enneenne.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=woojung.huh@microchip.com \
/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