| /openbmc/u-boot/doc/ |
| H A D | README.POST | 28 2) The results of tests shall be saved so that it will be possible to
56 A new optional module will be added to U-Boot, which will run POST
57 tests and collect their results at boot time. Also, U-Boot will
61 The list of available POST tests will be configured at U-Boot build
62 time. The POST layer will allow the developer to add any custom POST
63 tests. All POST tests will be divided into the following groups:
67 This group will contain those tests that run only once on
72 This group will contain those tests that do not take much
77 This group will contain POST tests that consume much time
82 This group will contain those tests that can be run manually.
[all …]
|
| /openbmc/linux/drivers/rtc/ |
| H A D | Kconfig | 19 Generic RTC class support. If you say yes here, you will
20 be allowed to plug one or more RTCs to your system. You will
29 If you say yes here, the system time (wall clock) will be set using
38 The RTC device that will be used to (re)initialize the system
46 system will need an external clock source (like an NTP server).
57 If you say yes here, the system time (wall clock) will be stored
114 Other RTCs will not be available through that API.
143 The emulation code will read the time from the hardware
159 will be called rtc-test.
173 will be called rtc-88pm860x.
[all …]
|
| /openbmc/linux/drivers/i2c/busses/ |
| H A D | Kconfig | 23 If you say yes to this option, support will be included for the SMB
29 will be called i2c-ali1535.
35 If you say yes to this option, support will be included for the SMB
41 will be called i2c-ali1563.
47 If you say yes to this option, support will be included for the
51 will be called i2c-ali15x3.
57 If you say yes to this option, support will be included for the AMD
63 will be called i2c-amd756.
69 Enabling this option will add specific SMBus support for the Tyan
72 and temperature sensors live. Saying yes here will give you access
[all …]
|
| /openbmc/linux/drivers/input/misc/ |
| H A D | Kconfig | 8 Say Y here, and a list of miscellaneous input drivers will be displayed.
24 will be called 88pm860x_onkey.
34 will be called 88pm80x_onkey.
44 will be called ab8500-ponkey.
54 module will be called ad714x.
64 module will be called ad714x-i2c.
74 module will be called ad714x-spi.
85 will be called ariel-pwrbutton.
95 module will be called arizona-haptics.
106 module will be called atc260x-onkey.
[all …]
|
| /openbmc/linux/drivers/input/touchscreen/ |
| H A D | Kconfig | 8 Say Y here, and a list of supported touchscreens will be displayed.
25 module will be called 88pm860x-ts.
38 on your board, you will also get hwmon interfaces for the voltage
44 module will be called ads7846.
57 module will be called ad7877.
68 module will be called ad7879.
78 module will be called ad7879-i2c.
90 module will be called ad7879-spi.
104 module will be called resistive-adc-touch.ko.
116 module will be called ar1021_i2c.
[all …]
|
| /openbmc/linux/drivers/media/i2c/ |
| H A D | Kconfig | 51 module will be called ar0521.
60 module will be called hi556.
69 module will be called hi846.
78 module will be called hi847.
87 module will be called imx208.
98 module will be called imx214.
108 module will be called imx219.
117 module will be called imx258.
135 module will be called imx290.
144 module will be called imx296.
[all …]
|
| /openbmc/linux/net/sched/ |
| H A D | Kconfig | 16 If you say N here, you will get the standard packet scheduler, which
17 is a FIFO (first come, first served). If you say Y here, you will be
31 This Quality of Service (QoS) support will enable you to use
37 If you say Y here and to "/proc file system" below, you will be able
60 module will be called sch_htb.
69 module will be called sch_hfsc.
78 module will be called sch_prio.
87 module will be called sch_multiq.
98 module will be called sch_red.
109 module will be called sch_sfb.
[all …]
|
| /openbmc/linux/drivers/comedi/ |
| H A D | Kconfig | 40 kernel: saying N will just cause the configurator to skip all
54 To compile this driver as a module, choose M here: the module will be
65 To compile this driver as a module, choose M here: the module will be
76 To compile this driver as a module, choose M here: the module will be
85 To compile this driver as a module, choose M here: the module will be
96 kernel: saying N will just cause the configurator to skip all
107 To compile this driver as a module, choose M here: the module will be
128 To compile this driver as a module, choose M here: the module will be
136 To compile this driver as a module, choose M here: the module will be
159 To compile this driver as a module, choose M here: the module will be
[all …]
|
| /openbmc/linux/drivers/media/usb/gspca/ |
| H A D | Kconfig | 17 module will be called gspca_main.
28 module will be called gspca_benq.
37 module will be called gspca_conex.
48 module will be called gspca_cpia1.
58 module will be called gspca_dtcs033.
67 module will be called gspca_etoms.
76 module will be called gspca_finepix.
85 module will be called gspca_jeilinj.
95 module will be called gspca_jl2005bcd.
104 module will be called gspca_kinect.
[all …]
|
| /openbmc/linux/drivers/hwmon/ |
| H A D | Kconfig | 24 will be called hwmon.
54 will be called abituguru.
68 will be called abituguru3.
86 will be called ad7314.
96 will be called ad7414.
106 will be called ad7418.
118 will be called adm1021.
129 will be called adm1025.
140 will be called adm1026.
151 will be called adm1029.
[all …]
|
| /openbmc/linux/drivers/iio/accel/ |
| H A D | Kconfig | 18 To compile this driver as a module, say M here: the module will
30 To compile this driver as a module, say M here: the module will be
46 will be called adxl313_i2c and you will also get adxl313_core
59 will be called adxl313_spi and you will also get adxl313_core
76 will be called adxl345_i2c and you will also get adxl345_core
90 will be called adxl345_spi and you will also get adxl345_core
108 will be called adxl355_i2c and you will also get adxl355_core
123 will be called adxl355_spi and you will also get adxl355_core
140 module will be called adxl367_spi.
151 module will be called adxl367_i2c.
[all …]
|
| /openbmc/linux/drivers/iio/adc/ |
| H A D | Kconfig | 36 To compile this driver as a module, choose M here: the module will be
54 To compile this driver as a module, choose M here: the module will be
67 module will be called ad7192.
79 To compile this driver as a module, choose M here: the module will be
91 module will be called ad7280a
101 module will be called ad7291.
111 module will be called ad7292.
123 module will be called ad7298.
139 module will be called ad7476.
155 module will be called ad7606_parallel.
[all …]
|
| /openbmc/linux/drivers/input/keyboard/ |
| H A D | Kconfig | 9 Say Y here, and a list of supported keyboards will be displayed.
28 module will be called adc_keys.
37 To compile this driver as a module, choose M here: the module will
51 module will be called adp5588-keys.
61 module will be called adp5589-keys.
71 module will be called amikbd.
84 You will also need to enable appropriate SPI master controllers:
89 module will be called applespi.
100 module will be called atakbd.
119 module will be called atkbd.
[all …]
|
| /openbmc/linux/drivers/hwmon/pmbus/ |
| H A D | Kconfig | 12 This driver can also be built as a module. If so, the module will
27 This driver can also be built as a module. If so, the module will
36 This driver can also be built as a module. If so, the module will
47 This driver can also be built as a module. If so, the module will
57 This driver can also be built as a module. If so, the module will
66 This driver can also be built as a module. If so, the module will
75 This driver can also be built as a module. If so, the module will
84 This driver can also be built as a module. If so, the module will
95 will be called delta-ahe50dc-fan.
104 This driver can also be built as a module. If so, the module will
[all …]
|
| /openbmc/linux/drivers/char/tpm/ |
| H A D | Kconfig | 15 say Yes and it will be accessible from within Linux. For
21 will be called tpm. If unsure, say N.
45 into the TPM kernel APIs. Physical layers will register against it.
54 specification (TPM2.0) say Yes and it will be accessible from
56 the module will be called tpm_tis.
66 specification (TPM2.0) say Yes and it will be accessible from
68 the module will be called tpm_tis_spi.
75 say Yes and it will be accessible from within Linux.
85 say Yes and it will be accessible from within Linux.
87 the module will be called tpm_tis_i2c.
[all …]
|
| /openbmc/linux/drivers/watchdog/ |
| H A D | Kconfig | 12 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
14 longer than 1 minute will result in rebooting the machine. This
57 /dev/watchdog file. If you say N here, the kernel will not update
59 enough your device will reboot.
156 A software monitoring watchdog. This will fail to reboot your system
157 from some situations that the hardware watchdog will recover
161 module will be called softdog.
169 is purely software, e.g. the panic governor will stall it!
182 which will be called bd9576_wdt.
194 which will be called da9052_wdt.
[all …]
|
| /openbmc/linux/drivers/iio/light/ |
| H A D | Kconfig | 20 To compile this driver as a module, choose M here: the module will
33 will be called adjd_s311.
44 module will be called adux1020.
54 module will be called al3010.
64 module will be called al3320a.
74 module will be called apds9300.
87 module will be called apds9960
98 For triggered measurements, you will need an additional trigger driver
102 will be called as73211.
111 To compile this driver as a module, choose M here: the module will
[all …]
|
| /openbmc/linux/drivers/pwm/ |
| H A D | Kconfig | 52 will be called pwm-ab8500.
64 will be called pwm-apple.
74 will be called pwm-atmel.
86 will be called pwm-atmel-hlcdc.
99 will be called pwm-atmel-tcb.
111 will be called pwm-bcm-iproc.
122 will be called pwm-bcm-kona.
132 will be called pwm-bcm2835.
142 will be called pwm-berlin.
153 will be called pwm-brcmstb.c.
[all …]
|
| /openbmc/linux/sound/pci/ |
| H A D | Kconfig | 22 will be called snd-ad1889.
34 will be called snd-als300
49 will be called snd-als4000.
63 will be called snd-ali5451.
75 will be called snd-asihpi.
86 will be called snd-atiixp.
96 will be called snd-atiixp-modem.
111 will be called snd-au8810.
125 will be called snd-au8820.
140 will be called snd-au8830.
[all …]
|
| /openbmc/docs/designs/oem/ibm/ |
| H A D | system-power-mode.md | 20 thermal monitoring and control. When a system is powered on, the OCCs will go to
21 an Active state. Anytime the OCC state changes to active, the BMC will need to
22 send a mode change and idle power saver (IPS) settings to the OCC. It will also
28 When a system is booted, the OCC will move to an ACTIVE state. In the ACTIVE
31 necessary to reset the OCC. When this happens, the OCC will move out of ACTIVE
32 state. After recovery, the OCC will be put back into the ACTIVE state. Anytime
34 runtime, the BMC will need to send the mode and the idle power saver settings to
40 Current Customer Settable System Power Modes that will be sent to the OCCs:
47 committee and will be used if/when approved.
57 Defaults will need to be configurable by the system owner (via JSON file)
[all …]
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | bpf_prog_run.rst | 45 the packet data that the BPF program will operate on. The kernel will then
46 execute the program and return the results to userspace. Note that programs will
48 will not actually be redirected or dropped, the program return code will just be
56 which can be used to execute XDP programs in a way where packets will actually
68 will not be returned to userspace; instead, the kernel will perform the
71 in the syscall parameters when running in this mode will be rejected. In
72 addition, not all failures will be reported back to userspace directly;
74 allocation errors) will halt execution and return an error. If an error occurs
76 execution will continue with the next repetition; these errors can be detected
80 the regular (non-live) mode. The XDP program will be executed as though the
[all …]
|
| /openbmc/docs/designs/ |
| H A D | power-recovery.md | 32 told) that chassis power can no longer be supported, but power to the BMC will
42 The goal of this design document is to describe how OpenBMC firmware will deal
66 - Do nothing when power is lost to the system (this will be the default)
77 policy. This is a separate instance of the `PowerRestorePolicy` which will be
79 setting is not the default, `None`, then software will execute the policy
92 - At a minimum, `PinholeReset` will be added. Others can be added as needed
103 this scenario after a BMC reboot, chassis-state-manager will check to see what
156 entire system is imminent(i.e. a blackout scenario where BMC will also lose
165 An application will be run after the chassis and host states have been
166 determined which will only run if the chassis power is not on.
[all …]
|
| /openbmc/u-boot/drivers/serial/ |
| H A D | Kconfig | 44 the full UART driver will be omitted, thus saving space.
54 the full UART driver will be omitted, thus saving space.
64 the full UART driver will be omitted, thus saving space.
180 the drivers may conflict and you will get strange output.
183 prompt "Select which UART will provide the debug UART"
191 You will need to provide parameters to make this work. The driver will
198 You will need to provide parameters to make this work. The driver will
206 You will need to provide parameters to make this work. The
207 driver will be available until the real driver model serial is
215 You will need to provide parameters to make this work. The
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
10 This will be one of the following strings:
32 Some regulator directories will contain a field called
36 This will be one of the following strings:
72 Each regulator directory will contain a field called
75 This will be one of the following strings:
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
[all …]
|
| /openbmc/linux/drivers/media/test-drivers/vidtv/ |
| H A D | vidtv_channel.h | 9 * When vidtv boots, it will create some hardcoded channels.
10 * Their services will be concatenated to populate the SDT.
11 * Their programs will be concatenated to populate the PAT
12 * Their events will be concatenated to populate the EIT
13 * For each program in the PAT, a PMT section will be created
14 * The PMT section for a channel will be assigned its streams.
15 * Every stream will have its corresponding encoder polled to produce TS packets
34 * When vidtv boots, it will create some hardcoded channels.
35 * Their services will be concatenated to populate the SDT.
36 * Their programs will be concatenated to populate the PAT
[all …]
|