Home
last modified time | relevance | path

Searched full:sensitive (Results 1 – 25 of 341) sorted by relevance

12345678910>>...14

/linux/drivers/irqchip/
H A Dqcom-pdc.c110 * Level sensitive active low LOW
111 * Rising edge sensitive NOT USED
112 * Falling edge sensitive LOW
113 * Dual Edge sensitive NOT USED
114 * Level sensitive active High HIGH
115 * Falling Edge sensitive NOT USED
116 * Rising edge sensitive HIGH
117 * Dual Edge sensitive HIGH
/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Dsnps,archs-idu-intc.txt21 4 = active high level-sensitive <<< DEFAULT
22 8 = NOT SUPPORTED (active low level-sensitive)
24 sensitive.
H A Dopen-pic.txt46 1 = active low level-sensitive
47 2 = active high level-sensitive
84 // Interrupt source '42' that is active high level-sensitive.
H A Dimg,pdc-intc.txt44 4 = active-high level-sensitive (required for perip irqs)
45 8 = active-low level-sensitive
102 // Interrupt source SysWake 0 that is active-low level-sensitive
H A Dnxp,lpc3220-mic.txt12 IRQ_TYPE_LEVEL_HIGH = active high level-sensitive,
13 IRQ_TYPE_LEVEL_LOW = active low level-sensitive.
H A Dinterrupts.txt75 4 = active high level-sensitive
76 8 = active low level-sensitive
/linux/Documentation/devicetree/bindings/mfd/
H A Dallwinner,sun4i-a10-ts.yaml33 allwinner,tp-sensitive-adjust:
71 /* sensitive/noisy touch panel */
72 allwinner,tp-sensitive-adjust = <0>;
/linux/Documentation/security/
H A Dself-protection.rst70 Function pointers and sensitive variables must not be writable
167 the kernel's preallocated stack space and into sensitive structures. Two
169 sensitive thread_info structure elsewhere, and adding a faulting memory
258 By performing a per-build randomization of the layout of sensitive
267 Since the locations of sensitive structures are the primary target for
270 addresses or other sensitive things like canary values).
275 Printing kernel addresses to userspace leaks sensitive information about
316 it should automatically censor sensitive values.
/linux/Documentation/devicetree/bindings/input/
H A Dmicrochip,cap11xx.yaml79 Higher value means more sensitive settings.
80 At the more sensitive settings, touches are detected for a smaller delta
107 sensitive.
119 to be more sensitive for proximity detection.
/linux/Documentation/virt/kvm/devices/
H A Dxics.rst77 * Level sensitive flag, 1 bit
79 This bit is 1 for a level-sensitive interrupt source, or 0 for
80 edge-sensitive (or MSI).
/linux/drivers/gpu/drm/
H A Ddrm_vblank_work.c15 * Many DRM drivers need to program hardware in a time-sensitive manner, many
18 * simply do said time-sensitive programming in the driver's IRQ handler,
24 * doesn't need to be concerned with extremely time-sensitive programming,
26 * hardware may require that certain time-sensitive programming be handled
41 * time-sensitive hardware programming on time, even when the system is under
/linux/tools/testing/selftests/tpm2/
H A Dtpm2.py554 sensitive = SensitiveCreate(user_auth=auth_value)
572 (len(auth_cmd), len(sensitive), len(public))
581 len(sensitive),
582 bytes(sensitive),
600 sensitive = SensitiveCreate(user_auth=auth_value, data=data)
610 (len(auth_cmd), len(sensitive), len(public))
619 len(sensitive),
620 bytes(sensitive),
/linux/Documentation/devicetree/bindings/gpio/
H A Dsodaville.txt16 4 - active high level-sensitive
17 8 - active low level-sensitive
H A Dnvidia,tegra20-gpio.yaml53 4 = active high level-sensitive.
54 8 = active low level-sensitive.
H A Dbrcm,brcmstb-gpio.yaml59 4 = active high level-sensitive
60 8 = active low level-sensitive
H A Dsocionext,uniphier-gpio.yaml35 4 = active high level-sensitive
36 8 = active low level-sensitive
/linux/Documentation/scheduler/
H A Dsched-eevdf.rst21 allows latency-sensitive tasks with shorter time slices to be prioritized,
32 which further facilitates the job of latency-sensitive applications.
/linux/Documentation/power/
H A Dswsusp.rst323 protect from leaking sensitive data after resume from suspend.
326 that keeps sensitive data in memory. The application itself prevents
329 your sensitive data are then stored in plaintext on disk. This means
330 that after resume your sensitive data are accessible to all
334 broken in weeks later and sensitive data which you thought were
350 suspend image to prevent sensitive data from being stolen after
/linux/security/
H A DKconfig.hardening168 the lifetime of any sensitive stack contents and reduces
312 prompt "Randomize layout of sensitive kernel structures"
345 Fully randomize the member layout of sensitive
361 Randomization of sensitive kernel structures will make a
/linux/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-image-source.rst58 The unit cell consists of the whole area of the pixel, sensitive and
59 non-sensitive.
H A Dcolorspaces.rst20 the human eye has color receptors that are sensitive to three different
22 color. Be glad you are not a mantis shrimp as those are sensitive to 12
110 human eye is more sensitive to differences in luminance than in color
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dbrcm,bcm2835-gpio.txt29 4 = active high level-sensitive.
30 8 = active low level-sensitive.
/linux/arch/arm64/kvm/vgic/
H A Dvgic-v2.c46 * - transferred as is in case of edge sensitive IRQs
47 * - set to the line-level (resample time) for level sensitive IRQs
113 * - for an edge sensitive IRQ the pending state is cleared in struct vgic_irq
114 * - for a level sensitive IRQ the pending state value is unchanged;
/linux/drivers/media/pci/tw5864/
H A Dtw5864-reg.h1951 * 0 Low threshold (More sensitive) (default)
1953 * 3 High threshold (Less sensitive)
1961 * 0 More Sensitive (default)
1963 * 15 Less Sensitive
1994 * 0 More sensitive (default)
1996 * 15 Less sensitive
2004 * 0 Motion is detected if 1 sub-cell has motion (More sensitive) (default)
2007 * 3 Motion is detected if 4 sub-cells have motion (Less sensitive)
2028 * 0 More Sensitive (default)
2030 * 15 Less Sensitive
[all …]
/linux/drivers/cpufreq/
H A DKconfig.x86190 Hardware feedback tells software how "sensitive" to frequency changes
191 the CPUs' workloads are. CPU-bound workloads will be more sensitive
193 workloads will be less sensitive -- they will not necessarily perform

12345678910>>...14