summaryrefslogtreecommitdiff
path: root/src/drivers/oxford/oxpcie/Kconfig
blob: 899a1533b70712fbb42ce3baea1b592fc4f5a596 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
config DRIVERS_OXFORD_OXPCIE
	bool "Oxford OXPCIe952"
	default n
	select HAVE_UART_MEMORY_MAPPED
	help
	  Support for Oxford OXPCIe952 serial port PCIe cards.
	  Currently only devices with the vendor ID 0x1415 and device ID
	  0xc158 will work.
	  NOTE: Right now you have to set the base address of your OXPCIe952
	  card to exactly the value that the device allocator would set them
	  later on, or serial console functionality will stop as soon as the
	  resource allocator assigns a new base address to the device.

config OXFORD_OXPCIE_BRIDGE_BUS
	hex "OXPCIe's PCIe bridge bus number"
	default 0x0
	depends on DRIVERS_OXFORD_OXPCIE
	help
	  While coreboot is executing code from ROM, the coreboot resource
	  allocator has not been running yet. Hence PCI devices living behind
	  a bridge are not yet visible to the system. In order to use an
	  OXPCIe952 based PCIe card, coreboot has to set up the PCIe bridge
	  that controls the OXPCIe952 controller first.

config OXFORD_OXPCIE_BRIDGE_DEVICE
	hex "OXPCIe's PCIe bridge device number"
	default 0x1c
	depends on DRIVERS_OXFORD_OXPCIE
	help
	  While coreboot is executing code from ROM, the coreboot resource
	  allocator has not been running yet. Hence PCI devices living behind
	  a bridge are not yet visible to the system. In order to use an
	  OXPCIe952 based PCIe card, coreboot has to set up the PCIe bridge
	  that controls the OXPCIe952 controller first.

config OXFORD_OXPCIE_BRIDGE_FUNCTION
	hex "OXPCIe's PCIe bridge function number"
	default 0x2
	depends on DRIVERS_OXFORD_OXPCIE
	help
	  While coreboot is executing code from ROM, the coreboot resource
	  allocator has not been running yet. Hence PCI devices living behind
	  a bridge are not yet visible to the system. In order to use an
	  OXPCIe952 based PCIe card, coreboot has to set up the PCIe bridge
	  that controls the OXPCIe952 controller first.

config OXFORD_OXPCIE_BRIDGE_SUBORDINATE
	hex "OXPCIe's PCIe bridge subordinate bus"
	default 0x3
	depends on DRIVERS_OXFORD_OXPCIE
	help
	  While coreboot is executing code from ROM, the coreboot resource
	  allocator has not been running yet. Hence PCI devices living behind
	  a bridge are not yet visible to the system. In order to use an
	  OXPCIe952 based PCIe card, coreboot has to set up the PCIe bridge
	  that controls the OXPCIe952 controller first.

config OXFORD_OXPCIE_BASE_ADDRESS
	hex "Base address for rom stage console"
	default 0xe0400000
	depends on DRIVERS_OXFORD_OXPCIE
	help
	  While coreboot is executing code from ROM, the coreboot resource
	  allocator has not been running yet. Hence PCI devices living behind
	  a bridge are not yet visible to the system. In order to use an
	  OXPCIe952 based PCIe card, coreboot has to set up a temporary address
	  for the OXPCIe952 controller.