From: Andrew Lunn <andrew@lunn.ch>
To: "Abdul Rahim, Faizal" <faizal.abdul.rahim@linux.intel.com>
Cc: David Laight <david.laight.linux@gmail.com>,
KhaiWenTan <khai.wen.tan@linux.intel.com>,
anthony.l.nguyen@intel.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
faizal.abdul.rahim@intel.com, hong.aun.looi@intel.com,
khai.wen.tan@intel.com, hector.blanco.alcaine@intel.com
Subject: Re: [PATCH iwl-next v4 0/3] igc: add support for forcing link speed without autonegotiation
Date: Thu, 7 May 2026 14:15:37 +0200 [thread overview]
Message-ID: <a74089d5-1b27-4d05-bd8c-9ec2226667be@lunn.ch> (raw)
In-Reply-To: <78e48cc4-759f-46e1-83c7-1c9442308ae3@linux.intel.com>
> I agree that for normal Ethernet use, auto-negotiation on both link
> partners is safer and avoids the issues you mentioned.
>
> The reason for this patch is the more specific PROFINET Fast Start Up
> (FSU) use case. For FSU, the requirement is different from normal Ethernet
> use. It is intended for deterministic startup, for example in industrial
> robot/tool-change applications.
>
> One of the startup optimizations is to use "fixed transmission parameters"
> instead of automatic detection in the profinet specification:
> https://us.profinet.com/profinet_tech/fast-start-up/
Automotive also have similar requirements. For them, Autoneg is slow,
takes around 1 second, where as a fixed link is operative very
fast. There are even some automotive ethernet devices which don't even
support autoneg.
So this use case makes sense to me, for embedded systems. If the
hardware can do it, any most PHYs can, i see no reason not to support
it. And anything using phylib gets it for free.
Andrew
prev parent reply other threads:[~2026-05-07 12:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 6:00 [PATCH iwl-next v4 0/3] igc: add support for forcing link speed without autonegotiation KhaiWenTan
2026-04-28 6:00 ` [PATCH iwl-next v4 1/3] igc: remove unused autoneg_failed field KhaiWenTan
2026-04-28 6:56 ` [Intel-wired-lan] " Paul Menzel
2026-04-28 10:39 ` Abdul Rahim, Faizal
2026-04-28 15:06 ` Paul Menzel
2026-05-06 6:07 ` Abdul Rahim, Faizal
2026-04-28 6:00 ` [PATCH iwl-next v4 2/3] igc: move autoneg-enabled settings into igc_handle_autoneg_enabled() KhaiWenTan
2026-04-28 6:00 ` [PATCH iwl-next v4 3/3] igc: add support for forcing link speed without autonegotiation KhaiWenTan
2026-04-30 13:50 ` Simon Horman
2026-05-06 6:25 ` Abdul Rahim, Faizal
2026-05-07 10:32 ` Simon Horman
2026-04-30 14:41 ` [PATCH iwl-next v4 0/3] " David Laight
2026-05-06 6:21 ` Abdul Rahim, Faizal
2026-05-06 9:40 ` David Laight
2026-05-07 9:03 ` Abdul Rahim, Faizal
2026-05-07 12:15 ` Andrew Lunn [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=a74089d5-1b27-4d05-bd8c-9ec2226667be@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=edumazet@google.com \
--cc=faizal.abdul.rahim@intel.com \
--cc=faizal.abdul.rahim@linux.intel.com \
--cc=hector.blanco.alcaine@intel.com \
--cc=hong.aun.looi@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=khai.wen.tan@intel.com \
--cc=khai.wen.tan@linux.intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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