| /linux/Documentation/ABI/testing/ |
| A D | sysfs-bus-iio-timer-stm32 | 37 OC4REF rising or falling edges generate pulses.
39 OC6REF rising or falling edges generate pulses.
41 OC4REF or OC6REF rising edges generate pulses.
43 OC4REF rising or OC6REF falling edges generate
46 OC5REF or OC6REF rising edges generate pulses.
48 OC5REF rising or OC6REF falling edges generate
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| A D | msi.txt | 57 MSI clients are devices which generate MSIs. For each MSI they wish to
58 generate, the doorbell and payload may be configured, though sideband
75 and the set of MSIs they can potentially generate.
112 /* Can only generate MSIs to msi_a */
121 * Can generate MSIs to either A or B.
131 * Can generate MSIs to all of the MSI controllers.
|
| A D | hisilicon,mbigen-v2.txt | 9 Hisilicon designed mbigen to collect and generate interrupt.
12 Non-pci devices can connect to mbigen and generate the
|
| /linux/Documentation/doc-guide/ |
| A D | parse-headers.rst | 6 order to describe the userspace API and to generate cross-references
8 userspace API files has an additional vantage: Sphinx will generate warnings
11 The :ref:`parse_headers.pl <parse_headers>` provide a way to generate such
84 The \ **ignore**\ means that it won't generate cross references for a
92 The \ **replace**\ means that it will generate cross references for a
162 It won't generate cross-references for \ **PRIVATE**\ .
|
| /linux/Documentation/kbuild/ |
| A D | gcc-plugins.rst | 73 **$(src)/scripts/gcc-plugins/gcc-generate-gimple-pass.h,
74 $(src)/scripts/gcc-plugins/gcc-generate-ipa-pass.h,
75 $(src)/scripts/gcc-plugins/gcc-generate-simple_ipa-pass.h,
76 $(src)/scripts/gcc-plugins/gcc-generate-rtl-pass.h**
78 These headers automatically generate the registration structures for
|
| /linux/Documentation/security/ |
| A D | IMA-templates.rst | 19 a new template is defined, the functions that generate and display
27 field, to generate and display data of a given type.
31 two functions, init() and show(), respectively to generate and display
41 mechanism) to generate a new measurement entry by using the template
76 - 'buf': the buffer data that was used to generate the hash without size limitations;
100 To specify the template descriptor to be used to generate measurement entries,
|
| A D | digsig.rst | 48 Signature header is used as an input to generate a signature.
82 to generate signatures, to load keys into the kernel keyring.
|
| /linux/include/crypto/ |
| A D | rng.h | 42 int (*generate)(struct crypto_rng *tfm, member
144 ret = crypto_rng_alg(tfm)->generate(tfm, src, slen, dst, dlen); in crypto_rng_generate()
|
| /linux/Documentation/devicetree/bindings/clock/ |
| A D | imx6sl-clock.yaml | 20 description: CCM provides 2 interrupt requests, request 1 is to generate
21 interrupt for frequency or mux change, request 2 is to generate
|
| A D | imx6sll-clock.yaml | 20 description: CCM provides 2 interrupt requests, request 1 is to generate
21 interrupt for frequency or mux change, request 2 is to generate
|
| A D | imx6ul-clock.yaml | 20 description: CCM provides 2 interrupt requests, request 1 is to generate
21 interrupt for frequency or mux change, request 2 is to generate
|
| A D | imx6sx-clock.yaml | 20 description: CCM provides 2 interrupt requests, request 1 is to generate
21 interrupt for frequency or mux change, request 2 is to generate
|
| A D | imx5-clock.yaml | 28 description: CCM provides 2 interrupt requests, request 1 is to generate
29 interrupt for frequency or mux change, request 2 is to generate
|
| A D | imx6q-clock.yaml | 20 description: CCM provides 2 interrupt requests, request 1 is to generate
21 interrupt for frequency or mux change, request 2 is to generate
|
| A D | imx31-clock.yaml | 87 description: CCM provides 2 interrupt requests, request 1 is to generate
89 to generate interrupt for DPTC when a voltage change is requested.
|
| A D | silabs,si570.txt | 21 order to generate the correct output frequencies. For more
28 - clock-frequency: Output frequency to generate. This defines the output
|
| /linux/Documentation/driver-api/acpi/ |
| A D | linuxized-acpica.rst | 174 scripts located in generate/linux folder.
210 upstream source code and generate the linuxized fix using the ACPICA
249 $ generate/linux/gen-patch.sh -u [commit ID]
259 You can generate the ACPICA release series yourself and rebase your code on
264 $ generate/linux/make-patches.sh -u [commit ID]
273 If you have local copies of both Linux and upstream ACPICA, you can generate
279 # generate/linux/divergence.sh -s ../linux
|
| /linux/arch/mips/bcm47xx/ |
| A D | Kconfig | 21 This will generate an image with support for SSB and MIPS32 R1 instruction set.
38 This will generate an image with support for BCMA and MIPS32 R2 instruction set.
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| A D | gpio-eic-sprd.txt | 20 and generate interrupts, since the EIC-latch does not depend on the APB
24 (microsecond resolution) to generate interrupts by level or edge trigger.
27 signal input register. It can generate interrupts by level or edge trigger
|
| /linux/Documentation/driver-api/ |
| A D | dcdbas.rst | 31 the SMI and provides a way for the application to generate the SMI.
45 3) Write "1" to smi_request to generate a calling interface SMI or
46 "2" to generate a raw SMI.
|
| /linux/Documentation/devicetree/bindings/net/ |
| A D | sti-dwmac.txt | 21 - st,ext-phyclk: valid only for RMII where PHY can generate 50MHz clock or
22 MAC can generate it.
|
| /linux/Documentation/devicetree/bindings/input/rmi4/ |
| A D | rmi_2d_sensor.txt | 30 to generate an interrupt in reduced reporting
33 to generate an interrupt in reduced reporting
|
| /linux/Documentation/admin-guide/ |
| A D | lockup-watchdogs.rst | 41 A periodic hrtimer runs to generate interrupts and kick the watchdog
47 generate a kernel warning or call panic, depending on the
59 two or three chances to generate an interrupt before the hardlockup
|
| A D | module-signing.rst | 62 will be loaded. All other modules will generate an error.
128 Cryptographic keypairs are required to generate and check signatures. A
129 private key is used to generate a signature and the corresponding public key is
136 default, the kernel build will automatically generate a new keypair using
164 It is also possible to manually generate the key private/public files using the
167 generate the public/private key files::
|
| /linux/tools/lib/traceevent/Documentation/ |
| A D | libtraceevent-header_page.txt | 45 generate the tracing data, which has no event/header_page. If the kernel is new,
64 printf ("%s kernel is used to generate the tracing data.\n",
|