| /Documentation/pcmcia/ |
| D | driver-changes.rst | 7 * pcmcia_loop_config() and autoconfiguration (as of 2.6.36)
20 * pcmcia_request_configuration -> pcmcia_enable_device (as of 2.6.36)
22 as it mirrors pcmcia_disable_device(). Configuration settings are now
26 * pcmcia_request_window changes (as of 2.6.36)
33 * pcmcia_request_io changes (as of 2.6.36)
40 * No dev_info_t, no cs_types.h (as of 2.6.36)
42 in PCMCIA device drivers. Also, do not include pcmcia/cs_types.h, as
45 * No dev_node_t (as of 2.6.35)
48 * New IRQ request rules (as of 2.6.35)
57 * no cs_error / CS_CHECK / CONFIG_PCMCIA_DEBUG (as of 2.6.33)
[all …]
|
| /Documentation/input/ |
| D | gamepad.rst | 16 As "gamepad" we define devices which roughly look like this::
45 differently labeled on most devices so we define them as NORTH,
51 Furthermore, many gamepads have a fancy branded button that is used as
70 an alias for BTN_SOUTH/BTN_A. It can be used to identify a gamepad as such.
74 Legacy drivers often don't comply to these rules. As we cannot change them
85 and one analog stick. It reports them as if it were a gamepad with only one
111 If only 2 action-buttons are present, they are reported as BTN_SOUTH and
117 If only 3 action-buttons are present, they are reported as (from left
119 If the buttons are aligned perfectly vertically, they are reported as
125 different formations. If diamond-shaped, they are reported as BTN_NORTH,
[all …]
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 20 default value, supported as read-only
24 supported as read-write
28 supported as read-write
35 supported as read-write
39 supported as read-write
43 supported as read-only
47 supported as read-only
51 supported as read-only
55 supported as read-only
|
| D | security-bugs.rst | 6 Linux kernel developers take security very seriously. As such, we'd
8 disclosed as quickly as possible. Please report security bugs to the
17 If you already have a fix, please include it with your report, as
22 As it is with any bug, the more information provided the easier it
39 as soon as they become available, this may be postponed at the request of
62 Fixes for sensitive bugs, such as those that might lead to privilege
71 the email Subject line with "[vs]" as described in the linux-distros wiki:
78 for reports or fixes, as this can needlessly complicate the process and
|
| /Documentation/networking/ |
| D | framerelay.txt | 3 Data Link Connection Identifier (DLCI) as its hardware address. Usually these
8 As such, a separate device is needed to accommodate the routing. Within the
11 The configuration script will ask you how many DLCIs you need, as well as
21 S508 are supported. This driver is currently set up for only FR, but as
23 them as well.
27 to specify the types of boards to be configured as FRADs, as well as perform
32 Additional FRAD device drivers can be added as hardware is available.
|
| D | ltpc.txt | 9 configuration dialog. You can also compile it as a module.
18 as the following to your /etc/lilo.conf:
26 If you load the driver as a module, you can pass the parameters "io=",
28 them as options in a configuration file in /etc/modprobe.d/ directory:
34 need to add a line such as:
55 compiled as a module, you will need to refer to it as "dummy0" or some
69 board. Set the switches so as not to conflict with other hardware.
101 Instead, you follow the same procedure as for doing IP in EtherTalk.
110 this, either compile the driver as a module, or pass the parameters
111 for the card to the kernel as described above.
[all …]
|
| D | xfrm_sync.txt | 10 the processing of the SA as accurate as possible if it has access to it.
15 with as minimal loss at failover time.
16 This way a backup stays as closely up-to-date as an active member.
43 A XFRM_MSG_NEWAE will have at least two TLVs (as is
69 message (kernel<->user) as well the cause (config, query or event).
95 This is a timer value in milliseconds which is used as the nagle
106 in order to not change existing applications such as racoon
139 XFRM_MSG_NEWAE is also issued to any listeners as described in iii).
141 ii) kernel->user direction as a response to XFRM_MSG_GETAE
146 iii) kernel->user to report as event if someone sets any values or
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | rt5659.txt | 25 1: using IN2N pin as dmic1 data pin
26 2: using GPIO5 pin as dmic1 data pin
27 3: using GPIO9 pin as dmic1 data pin
28 4: using GPIO11 pin as dmic1 data pin
32 1: using IN2P pin as dmic2 data pin
33 2: using GPIO6 pin as dmic2 data pin
34 3: using GPIO10 pin as dmic2 data pin
35 4: using GPIO12 pin as dmic2 data pin
39 1: using JD3 as JD source
|
| D | rt5645.txt | 24 1: using IN2P pin as dmic1 data pin
25 2: using GPIO6 pin as dmic1 data pin
26 3: using GPIO10 pin as dmic1 data pin
27 4: using GPIO12 pin as dmic1 data pin
31 1: using IN2N pin as dmic2 data pin
32 2: using GPIO5 pin as dmic2 data pin
33 3: using GPIO11 pin as dmic2 data pin
|
| /Documentation/devicetree/bindings/input/ |
| D | nvidia,tegra20-kbc.txt | 3 can be configured as row or column. The maximum column pin can be 8
10 - nvidia,kbc-row-pins: The KBC pins which are configured as row. This is an
11 array of pin numbers which is used as rows.
12 - nvidia,kbc-col-pins: The KBC pins which are configured as column. This is an
13 array of pin numbers which is used as column.
14 - linux,keymap: The keymap for keys as described in the binding document
26 - linux,fn-keymap: a second keymap, same specification as the
32 - wakeup-source: configure keyboard as a wakeup source for suspend/resume
46 nvidia,kbc-row-pins = <0 1 2>; /* pin 0, 1, 2 as rows */
47 nvidia,kbc-col-pins = <11 12 13>; /* pin 11, 12, 13 as columns */
|
| /Documentation/misc-devices/ |
| D | pci-endpoint-test.txt | 3 This driver should be used as a host side driver if the root complex is
25 should be passed as argument.
28 to be tested should be passed as argument.
30 to be tested should be passed as argument.
32 should be passed as argument (0: Legacy, 1:MSI, 2:MSI-X).
35 as argument.
37 as argument.
39 as argument.
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-entries | 12 cannot ensure that the data as exported to userland is
15 DMI is structured as a large table of entries, where
17 length of the entry, as well as a firmware-provided
33 doesn't matter), they will be represented in sysfs as
45 assigned entry handles as the kernel itself makes no
46 guarantees that handles as exported are unique, and
51 exported as attributes:
56 length : The length of the entry, as presented in the
70 as found in the directory name. It indicates
73 given type. This value is the same as found
[all …]
|
| D | sysfs-firmware-qemu_fw_cfg | 7 (fw_cfg) device, originally intended as a way for the host to
11 useful as an out-of-band, asynchronous mechanism for providing
22 with the file directory), as there is no way to determine the
37 displayed as entries named after their unique selector key
46 as attributes:
48 name : The 56-byte nul-terminated ASCII string used as the
50 size : The length of the blob, as given in the fw_cfg
52 key : The value of the blob's selector key as given in the
53 fw_cfg directory. This value is the same as used in
83 "basename", as illustrated below (assume current directory is
[all …]
|
| D | configfs-usb-gadget-mass-storage | 21 Required if LUN is not marked as removable.
24 is enabled as well as when it was impossible
26 removable - Flag specifying that LUN shall be indicated as
28 cdrom - Flag specifying that LUN shall be reported as
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | lm87.txt | 10 - has-temp3: This configures pins 18 and 19 to be used as a second
12 are configured as voltage input pins in0 and in5.
14 - has-in6: When set, pin 5 is configured to be used as voltage input
15 in6. Otherwise the pin is set as FAN1 input.
17 - has-in7: When set, pin 6 is configured to be used as voltage input
18 in7. Otherwise the pin is set as FAN2 input.
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti-sysc.txt | 4 hardware for devices connected to various interconnects such as L3
43 target module in question such as revision, sysc and syss
46 interconnect target module in question such as
52 multiple ranges such as device L4 range for control and
58 SYSCONFIG register as documented in the Technical Reference
62 target module as documented in the TRM for SYSCONFIG
66 target module as documented in the TRM for SYSCONFIG
72 - ti,syss-mask optional mask of reset done status bits as described in the
77 - clocks clock specifier for each name in the clock-names as
81 mode as for example omap4 L4_CFG_CLKCTRL
[all …]
|
| /Documentation/netlabel/ |
| D | introduction.rst | 24 engine will handle those tasks as well. Other kernel subsystems should
37 formatting of these NetLabel messages as well as the Generic NETLINK family
38 names can be found in the 'net/netlabel/' directory as comments in the
39 header files as well as in 'include/net/netlabel.h'.
51 'include/net/netlabel.h' header file as well as the 'lsm_interface.txt' file
|
| /Documentation/timers/ |
| D | timekeeping.rst | 17 on this timeline, providing facilities such as high-resolution timers.
32 It will ideally NEVER stop ticking as long as the system is running. It
35 The clock source shall have as high resolution as possible, and the frequency
36 shall be as stable and correct as possible as compared to a real-world wall
55 into a nanosecond value as an unsigned long long (unsigned 64 bit) number.
57 mathematical sense is not desirable: instead the number is taken as close as
64 to aid in providing these mult and shift values, such as
68 factors using the frequency of the clock source as the only input.
95 fire interrupts, so as to trigger events on the system timeline. On an SMP
115 implementation is not provided, the system jiffy counter will be used as
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-max77620.txt | 3 Device has 8 GPIO pins which can be configured as GPIO as well as the
18 The pin configurations are defined as child of the pinctrl states node. Each
28 Following are optional properties defined as pinmux DT binding document
69 selected as FPS0, FPS1 or FPS2.
76 selected as FPS0, FPS1 or FPS2.
78 - maxim,suspend-fps-source: This is same as property
83 - maxim,suspend-fps-power-up-slot: This is same as property
89 FPS source is selected as FPS0, FPS1 or
91 - maxim,suspend-fps-power-down-slot: This is same as property
97 FPS source is selected as FPS0, FPS1 or
|
| D | renesas,rza1-pinctrl.txt | 106 When multiple pins are required to be configured as part of the same
107 alternate function they shall be specified as members of the same
113 Integers values in "pinmux" argument list are assembled as:
122 operations. output-low can be used alternatively, as line value is
140 Pin #0 on port #3 is configured as alternate function #6.
141 Pin #2 on port #3 is configured as alternate function #4.
152 Pin #4 on port #1 is configured as alternate function #1.
153 Pin #5 on port #1 is configured as alternate function #1.
158 Configure TIOC0A as software driven input and TIOC0B as software driven
181 Pin #0 on port #4 is configured as alternate function #2 with IO direction
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | legacy.rst | 22 non-dedicated pin can be configured as a GPIO; and most chips have at least
38 of pins configured as "output", which is very useful in such "wire-OR"
42 - Inputs can often be used as IRQ signals, often edge triggered but
43 sometimes level triggered. Such IRQs may be configurable as system
46 - Usually a GPIO will be configurable as either input or output, as needed
69 One platform might implement it as simple inline functions accessing chip
73 in this document, but drivers acting as clients to the GPIO interface must
80 GPIO calls are available, either as "real code" or as optimized-away stubs,
95 reserves "negative" numbers for other purposes like marking signals as
97 touch the underlying hardware treats these integers as opaque cookies.
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,vic.txt | 12 - interrupt-controller : Identifies the node as an interrupt controller
13 - #interrupt-cells : The number of cells to define the interrupts. Must be 1 as
26 configured as wake up source for the system. Order of bits is the same as for
28 configured as a wake up source for the system. If unspecied, defaults to all
29 interrupt sources configurable as wake up sources.
|
| /Documentation/crypto/ |
| D | intro.rst | 7 The kernel crypto API offers a rich set of cryptographic ciphers as well
8 as other data transformation mechanisms and methods to invoke these.
18 The kernel crypto API refers to all algorithms as "transformations".
21 transformations and handles them the same way as ciphers.
30 This specification is intended for consumers of the kernel crypto API as
31 well as for developers implementing ciphers. This API specification,
34 transformations (such as CRC or even compression algorithms) that can
56 to as a "cipher handle". Such a cipher handle is always subject to the
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-thunderx.txt | 5 - gpio-controller: Marks the device node as a GPIO controller.
8 - Second cell is a standard generic flag bitfield as described in gpio.txt.
11 - compatible: "cavium,thunder-8890-gpio", unused as PCI driver binding is used.
12 - interrupt-controller: Marks the device node as an interrupt controller.
16 - Second cell is triggering flags as defined in interrupts.txt.
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
22 is affected by the state changes, this strategy is referred to as the
25 The other strategy, referred to as the :doc:`working-state power management
27 components of the system, as needed, in the working state. In consequence, if
29 correspond to any particular physical configuration of it, but can be treated as
37 If all of the system components are active, the system as a whole is regarded as
40 as a whole is regarded as "runtime idle" which may be very close to a sleep
|