On Sun, Apr 30, 2023 at 05:24:26PM -0400, Jim Quinlan wrote:
> I've been maintaining this driver for over eight years or so and we've
> done fine with the HW default completion timeout value.
> Only recently has a major customer requested that this timeout value
> be changed, and their reason was so they could
> avoid a CPU abort when using L1SS.
>
> Now we could set this value to a big number for all cases and not
> require "brcm,completion-timeout-us". I cannot see any
> downsides, other than another customer coming along asking us to
> double the default or lessen it.
The Completion Timeout is configurable in the Device Control 2 Register
(PCIe r2.1 sec 7.8.16). Your controller does expose that register:
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
AtomicOpsCtl: ReqEn- EgressBlck-
Why does your controller allow configuration of the timeout in a
proprietary register in addition to DevCtl2?
If you make the Completion Timeout configurable, please do so in
a spec-compliant way, i.e. via DevCtl2, so that it works for
other products as well.
If the proprietary register has advantages over DevCtl2 (e.g.
finer granularity), perhaps you can divert accesses to the
Completion Timeout Value in DevCtl2 to your proprietary register.
Thanks,
Lukas
