| /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 …]
|
| /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 …]
|
| /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 …]
|
| /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 …]
|
| /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.
60 into the TPM kernel APIs. Physical layers will register against it.
69 specification (TPM2.0) say Yes and it will be accessible from
71 the module will be called tpm_tis.
81 specification (TPM2.0) say Yes and it will be accessible from
83 the module will be called tpm_tis_spi.
90 say Yes and it will be accessible from within Linux.
100 say Yes and it will be accessible from within Linux.
102 the module will be called tpm_tis_i2c.
[all …]
|
| /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 …]
|
| /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 …]
|
| /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 …]
|
| H A D | sysfs-power | 5 The /sys/power directory will contain files that will
31 supported). The mode that will be used on subsequent attempts
48 the name of the method by which the system will be put to
51 'firmware' - means that the memory image will be saved to disk
53 firmware will handle the system suspend.
55 'platform' - the memory image will be saved by the kernel and
56 the system will be put to sleep by the platform driver (e.g.
59 'shutdown' - the memory image will be saved by the kernel and
60 the system will be powered off.
62 'reboot' - the memory image will be saved by the kernel and
[all …]
|
| /linux/tools/testing/ktest/ |
| H A D | sample.conf | 5 # ktest.pl is run from. By default, ktest.pl will look for a file
26 # Each TEST_START label will set up a new test. If you want to
29 # to iterate. If the ITERATE is left off, the test will only
61 # The above will run the first test with MIN_CONFIG set to
62 # /home/test/config-test-1. Then 10 tests will be executed
73 # The above will ignore the first MIN_CONFIG. If you want to
78 # ktest will fail to execute, and no tests will run.
89 # been defined previously. It will only override options that
91 # in a non override section will still error. The same option
103 # The above will process the DEFAULTS section if the config
[all …]
|
| /linux/Documentation/arch/arm64/ |
| H A D | gcs.rst | 47 * GCS specific errors (those reported with EC 0x2d) will be reported as
56 in LR match those in the GCS, the LR will be ignored. This is not supported
78 * Any unknown flags will cause PR_SET_SHADOW_STACK_STATUS to return -EINVAL.
82 status of the specified GCS mode bits will be rejected.
91 thread that called them, any other running threads will be unaffected.
102 the stack will remain allocated for the lifetime of the thread. At present
103 any attempt to reenable GCS for the thread will be rejected, this may be
106 * It should be noted that since enabling GCS will result in GCS becoming
109 usage will be that GCS is enabled very early in execution of a program.
116 * When GCS is enabled for a thread a new Guarded Control Stack will be
[all …]
|
| /linux/drivers/usb/serial/ |
| H A D | Kconfig | 19 module will be called usbserial.
27 If you say Y here, it will be possible to use a USB to serial
34 (/dev/tty0) will still be used as the system console by default, but
41 kernel will automatically use the first USB to serial converter
77 will be called usb-serial-simple.
85 will be called aircable.
94 module will be called ark3116
104 module will be called belkin_sa.
113 module will be called ch341.
123 module will be called whiteheat.
[all …]
|
| /linux/drivers/iio/dac/ |
| H A D | Kconfig | 18 module will be called ad3530r.
33 module will be called ad3552r-hs.
49 module will be called ad3552r.
63 module will be called ad5064.
73 To compile this driver as module choose M here: the module will be called
86 To compile this driver as module choose M here: the module will be called
96 To compile this driver as module choose M here: the module will be called
110 module will be called ad5446.
120 module will be called ad5449.
135 module will be called ad5592r.
[all …]
|
| /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 …]
|
| /linux/drivers/input/joystick/ |
| H A D | Kconfig | 11 and the list of supported devices will be displayed. This option
34 module will be called analog.
44 module will be called a3d.
55 module will be called adc-joystick.
66 module will be called adi.
75 module will be called cobra.
85 module will be called gf2k.
95 module will be called grip.
105 module will be called grip_mp.
115 module will be called guillemot.
[all …]
|
| /linux/Documentation/userspace-api/ |
| H A D | seccomp_filter.rst | 53 The BPF program will be executed over struct seccomp_data
64 will contain the filter program. If the program is invalid, the
65 call will return -1 and set errno to ``EINVAL``.
68 processes will be constrained to the same filters and system
73 true, ``-EACCES`` will be returned. This requirement ensures that filter
78 additional filters may be layered on which will increase evaluation
89 call will always use the highest precedent value. (For example,
90 ``SECCOMP_RET_KILL_PROCESS`` will always take precedence.)
97 will be ``SIGSYS``, not ``SIGKILL``.
101 system call. The exit status of the task (``status & 0x7f``) will
[all …]
|
| /linux/sound/isa/ |
| H A D | Kconfig | 40 will be called snd-adlib.
55 will be called snd-ad1816a.
68 will be called snd-ad1848.
83 will be called snd-als100.
96 will be called snd-azt1605.
109 will be called snd-azt2316.
123 will be called snd-azt2320.
135 will be called snd-cmi8328.
148 will be called snd-cmi8330.
159 will be called snd-cs4231.
[all …]
|
| /linux/Documentation/filesystems/ |
| H A D | fiemap.rst | 28 flags, it will return EBADR and the contents of fm_flags will contain
30 with all flags passed, the contents of fm_flags will be unmodified.
38 fm_extents[] array is ignored (no extents will be returned), and the
39 fm_mapped_extents count will hold the number of extents needed in
46 If this flag is set, the kernel will sync the file before mapping extents.
49 If this flag is set, the extents returned will describe the inodes
61 fm_extent_count. The number of extents mapped by kernel will be
65 array will be returned and fm_mapped_extents will be equal to
66 fm_extent_count. In that case, the last extent in the array will not
67 complete the requested range and will not have the FIEMAP_EXTENT_LAST
[all …]
|
| /linux/drivers/staging/greybus/ |
| H A D | Kconfig | 12 will be called gb-audio.ko
23 will be called gb-audio-codec.ko
33 will be called gb-bootrom.ko
43 will be called gb-camera.ko
53 will be called gb-firmware.ko
63 will be called gb-hid.ko
73 will be called gb-light.ko
82 will be called gb-log.ko
91 will be called gb-log.ko
101 will be called gb-power-supply.ko
[all …]
|
| /linux/Documentation/arch/s390/ |
| H A D | common_io.rst | 19 The given devices will be ignored by the common I/O-layer; no detection
20 and device sensing will be done on any of those devices. The subchannel to
21 which the device in question is attached will be treated as if no device was
29 give a device number 0xabcd, it will be interpreted as 0.0.abcd.
34 operator). The '!' operator will cause the I/O-layer to _not_ ignore a device.
42 will ignore all devices ranging from 0.0.0023 to 0.0.0042 and the device
49 will ignore all devices but 0.0.4711, 0.0.fd00, 0.0.fd01, 0.0.fd02.
62 "free all" will un-ignore all ignored devices,
63 "free <device range>, <device range>, ..." will un-ignore the specified
69 will un-ignore devices 0.0.0030 to 0.0.0032 and will leave devices 0.0.0023
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H A D | transactional_memory.rst | 48 references will complete in one go if there are no conflicts with other
54 lwarx/stwcx), either *both* SAVINGS_ACCT(r3) and CURRENT_ACCT(r3) will be
55 updated, or neither will be updated.
58 transaction, the transaction will be aborted by the CPU. Register and memory
59 state will roll back to that at the 'tbegin', and control will continue from
60 'tbegin+4'. The branch to abort_handler will be taken this second time; the
72 - See the ISA for full documentation of everything that will abort transactions.
78 Syscalls made from within an active transaction will not be performed and the
79 transaction will be doomed by the kernel with the failure code TM_CAUSE_SYSCALL
86 effects will be persistent, independent of transaction success or failure. No
[all …]
|
| /linux/drivers/iio/pressure/ |
| H A D | Kconfig | 17 will be called abp060mg.
45 will be called bmp280 and you will also get bmp280-i2c for I2C
68 will be called cros_ec_baro.
80 will be called dlhl60d.
90 This driver can also be built as a module. If so, the module will be
104 will be called hid-sensor-press.
115 will be called hp03.
129 will be called hsc030pa.
150 will be called icp10100.
164 will be called mpl115_i2c.
[all …]
|
| /linux/drivers/platform/chrome/ |
| H A D | Kconfig | 14 If you say N, all options in this submenu will be skipped and disabled.
27 The module will be called chromeos_acpi.
37 The module will be called chromeos_laptop.
51 The module will be called chromeos_pstore.
62 module will be called chromeos_tbmc.
72 devices. The driver will probe the correct component variant in
86 module will be called cros_ec.
95 a checksum. Failing accesses will be retried three times to
108 module will be called cros_ec_rpmsg.
121 module will be called cros_ec_ishtp.
[all …]
|
| /linux/drivers/i2c/muxes/ |
| H A D | Kconfig | 14 If you say yes to this option, support will be included for an
20 will be called i2c-arb-gpio-challenge.
26 If you say yes to this option, support will be included for a
32 will be called i2c-mux-gpio.
39 If you say yes to this option, support will be included for a
45 will be called i2c-mux-gpmux.
56 will be called i2c-mux-ltc4306.
65 will be called i2c-mux-pca9541.
75 will be called i2c-mux-pca954x.
82 If you say yes to this option, support will be included for an I2C
[all …]
|
| /linux/drivers/input/serio/ |
| H A D | Kconfig | 18 module will be called serio.
41 module will be called i8042.
56 module will be called serport.
69 module will be called ct82c710.
87 module will be called parkbd.
98 module will be called rpckbd.
120 module will be called gscps2.
136 By itself this option is rather useless, but enabling it will
157 module will be called pcips2.
167 module will be called maceps2.
[all …]
|