src/sys/dev/ntb/ntb.h, branch stable/13 FreeBSD source tree ntb_hw_plx: Workaround read-only scratchpad registers 2024-02-05T20:39:58+00:00 Alexander Motin mav@FreeBSD.org 2024-01-27T21:51:46+00:00 7393d37b12249aa26b0336136790cbcb33b690c2 On several systems we've noticed that when NTB link goes down, the Physical Layer User Test Pattern registers we use as additional scratchpad registers (that is explicitly allowed by the chip specs) become read-only for about 100us. I see no explanation for this in the chip specs, neither why it was not seen before, may be a race. Since we do need these registers, workaround it by repeating writes until we succeed or 1ms timeout expire. MFC after: 1 week (cherry picked from commit 3883c6fbf232452098ba6ea802ef1426d83d2d68) 
On several systems we've noticed that when NTB link goes down, the
Physical Layer User Test Pattern registers we use as additional
scratchpad registers (that is explicitly allowed by the chip specs)
become read-only for about 100us.  I see no explanation for this in
the chip specs, neither why it was not seen before, may be a race.
Since we do need these registers, workaround it by repeating writes
until we succeed or 1ms timeout expire.

MFC after:	1 week

(cherry picked from commit 3883c6fbf232452098ba6ea802ef1426d83d2d68)
sys: Remove $FreeBSD$: two-line .h pattern 2023-08-23T17:43:20+00:00 Warner Losh imp@FreeBSD.org 2023-08-22T01:31:02+00:00 f8167e0404dab9ffeaca95853dd237ab7c587f82 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ Similar commit in current: (cherry picked from commit 95ee2897e98f) 
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/

Similar commit in current:
(cherry picked from commit 95ee2897e98f)
Make ntb(4) send bus_get_dma_tag() requests to parent buses passing real 2019-11-14T04:34:58+00:00 Alexander Motin mav@FreeBSD.org 2019-11-14T04:34:58+00:00 7f215e071e924e6dae7fdab1d2f131c730c4e7b2 bus' child pointers instead of grandchilds. DMAR does not like requests from devices not parented directly by PCI. MFC after: 2 weeks 
bus' child pointers instead of grandchilds.

DMAR does not like requests from devices not parented directly by PCI.

MFC after:	2 weeks
Add driver for NTB in AMD SoC. 2019-07-02T05:25:18+00:00 Alexander Motin mav@FreeBSD.org 2019-07-02T05:25:18+00:00 6683132d54bd6d589889e43dabdc53d35e38a028 This patch is the driver for NTB hardware in AMD SoCs (ported from Linux) and enables the NTB infrastructure like Doorbells, Scratchpads and Memory window in AMD SoC. This driver has been validated using ntb_transport and if_ntb driver already available in FreeBSD. Submitted by: Rajesh Kumar <rajesh1.kumar@amd.com> MFC after: 1 month Relnotes: yes Differential Revision: https://reviews.freebsd.org/D18774 
This patch is the driver for NTB hardware in AMD SoCs (ported from Linux)
and enables the NTB infrastructure like Doorbells, Scratchpads and Memory
window in AMD SoC. This driver has been validated using ntb_transport and
if_ntb driver already available in FreeBSD.

Submitted by:	Rajesh Kumar <rajesh1.kumar@amd.com>
MFC after:	1 month
Relnotes:	yes
Differential Revision:	https://reviews.freebsd.org/D18774
Make NTB drivers report more info via NewBus methods. 2017-09-02T11:56:16+00:00 Alexander Motin mav@FreeBSD.org 2017-09-02T11:56:16+00:00 b7dd3fbedee199e37d7f8011f9e405716aa7781c MFC after: 12 days 
MFC after:	12 days
Once more refactor KPI between NTB hardware and consumers. 2016-07-28T10:48:20+00:00 Alexander Motin mav@FreeBSD.org 2016-07-28T10:48:20+00:00 4490696b3edf3ed9be81e695fb9dba03c94f89c8 New design allows hardware resources to be split between several consumers. For example, one BAR can be dedicated for remote memory access, while other resources can be used for packet transport for virtual Ethernet interface. And even without resource split, this code allows to specify which consumer driver should attach the hardware. From some points this makes the code even closer to Linux one, even though Linux does not provide the described flexibility. 
New design allows hardware resources to be split between several consumers.
For example, one BAR can be dedicated for remote memory access, while other
resources can be used for packet transport for virtual Ethernet interface.
And even without resource split, this code allows to specify which consumer
driver should attach the hardware.

From some points this makes the code even closer to Linux one, even though
Linux does not provide the described flexibility.
NewBus'ify NTB subsystem. 2016-07-09T11:20:42+00:00 Alexander Motin mav@FreeBSD.org 2016-07-09T11:20:42+00:00 9a5325c205f3e0088bd0be7d25185805c3bf45f0 This follows NTB subsystem modularization in Linux, tuning it to FreeBSD native NewBus interfaces. This change allows to support different types of hardware with different drivers, support multiple NTB instances in a system, ntb_transport module use for needs other then if_ntb, etc. Sponsored by: iXsystems, Inc. 
This follows NTB subsystem modularization in Linux, tuning it to FreeBSD
native NewBus interfaces.  This change allows to support different types
of hardware with different drivers, support multiple NTB instances in a
system, ntb_transport module use for needs other then if_ntb, etc.

Sponsored by:	iXsystems, Inc.