Home
last modified time | relevance | path

Searched +full:interrupt +full:- +full:less (Results 1 – 25 of 1017) sorted by relevance

12345678910>>...41

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/devfreq/
Drk3399_dmc.txt4 - compatible: Must be "rockchip,rk3399-dmc".
5 - devfreq-events: Node to get DDR loading, Refer to
7 rockchip-dfi.txt
8 - clocks: Phandles for clock specified in "clock-names" property
9 - clock-names : The name of clock used by the DFI, must be
11 - operating-points-v2: Refer to Documentation/devicetree/bindings/opp/opp.txt
13 - center-supply: DMC supply node.
14 - status: Marks the node enabled/disabled.
17 - interrupts: The CPU interrupt number. The interrupt specifier
18 format depends on the interrupt controller.
[all …]
/kernel/linux/linux-6.6/Documentation/usb/
Dohci.rst5 23-Aug-2002
7 The "ohci-hcd" driver is a USB Host Controller Driver (HCD) that is derived
8 from the "usb-ohci" driver from the 2.4 kernel series. The "usb-ohci" code
20 - improved robustness; bugfixes; and less overhead
21 - supports the updated and simplified usbcore APIs
22 - interrupt transfers can be larger, and can be queued
23 - less code, by using the upper level "hcd" framework
24 - supports some non-PCI implementations of OHCI
25 - ... more
27 The "ohci-hcd" driver handles all USB 1.1 transfer types. Transfers of all
[all …]
Dehci.rst5 27-Dec-2002
8 USB 2.0-capable host controller hardware. The USB 2.0 standard is
11 - "High Speed" 480 Mbit/sec (60 MByte/sec)
12 - "Full Speed" 12 Mbit/sec (1.5 MByte/sec)
13 - "Low Speed" 1.5 Mbit/sec
31 While usb-storage devices have been available since mid-2001 (working
34 appear to be on hold until more systems come with USB 2.0 built-in.
39 other changes to the Linux-USB core APIs, including the hub driver,
43 - David Brownell
56 --------------
[all …]
/kernel/linux/linux-5.10/Documentation/usb/
Dohci.rst5 23-Aug-2002
7 The "ohci-hcd" driver is a USB Host Controller Driver (HCD) that is derived
8 from the "usb-ohci" driver from the 2.4 kernel series. The "usb-ohci" code
20 - improved robustness; bugfixes; and less overhead
21 - supports the updated and simplified usbcore APIs
22 - interrupt transfers can be larger, and can be queued
23 - less code, by using the upper level "hcd" framework
24 - supports some non-PCI implementations of OHCI
25 - ... more
27 The "ohci-hcd" driver handles all USB 1.1 transfer types. Transfers of all
[all …]
Dehci.rst5 27-Dec-2002
8 USB 2.0-capable host controller hardware. The USB 2.0 standard is
11 - "High Speed" 480 Mbit/sec (60 MByte/sec)
12 - "Full Speed" 12 Mbit/sec (1.5 MByte/sec)
13 - "Low Speed" 1.5 Mbit/sec
31 While usb-storage devices have been available since mid-2001 (working
34 appear to be on hold until more systems come with USB 2.0 built-in.
39 other changes to the Linux-USB core APIs, including the hub driver,
43 - David Brownell
56 --------------
[all …]
/kernel/linux/linux-6.6/drivers/gpu/drm/kmb/
Dkmb_crtc.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright © 2018-2020 Intel Corporation
31 struct drm_device *dev = crtc->dev; in kmb_crtc_enable_vblank()
34 /* Clear interrupt */ in kmb_crtc_enable_vblank()
36 /* Set which interval to generate vertical interrupt */ in kmb_crtc_enable_vblank()
39 /* Enable vertical interrupt */ in kmb_crtc_enable_vblank()
47 struct drm_device *dev = crtc->dev; in kmb_crtc_disable_vblank()
50 /* Clear interrupt */ in kmb_crtc_disable_vblank()
52 /* Disable vertical interrupt */ in kmb_crtc_disable_vblank()
71 struct drm_device *dev = crtc->dev; in kmb_crtc_set_mode()
[all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/graniterapids/
Dpipeline.json21less than MAX. The reset value to the counter is not clocked immediately so the overflow status bi…
29less than MAX. The reset value to the counter is not clocked immediately so the overflow status bi…
48 "BriefDescription": "Number of instructions retired. Fixed Counter - architectural event",
51 … instructions retired - an Architectural PerfMon event. Counting continues during hardware interru…
56 "BriefDescription": "Number of instructions retired. General Counter - architectural event",
60 … instructions retired - an Architectural PerfMon event. Counting continues during hardware interru…
72 … the Topdown Slots event that were not consumed by the back-end pipeline due to lack of back-end r…
75-end pipeline due to lack of back-end resources, as a result of memory subsystem delays, execution…
80 …"BriefDescription": "TMA slots available for an unhalted logical processor. Fixed counter - archit…
82-width of the narrowest pipeline as employed by the Top-down Microarchitecture Analysis method (TM…
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/light/
Dopt3001.txt3 The driver supports interrupt-driven and interrupt-less operation, depending
4 on whether an interrupt property has been populated into the DT. Note that
12 - compatible: should be "ti,opt3001"
13 - reg: the I2C address of the sensor
16 - interrupts: interrupt mapping for GPIO IRQ (configure for falling edge)
23 interrupt-parent = <&gpio1>;
/kernel/linux/linux-6.6/arch/x86/include/asm/
Dhpet.h1 /* SPDX-License-Identifier: GPL-2.0 */
59 * Min HPET period is 10^5 femto sec just for safety. If it is less than this,
60 * then 32 bit HPET counter wrapsaround in less than 0.5 sec.
79 #include <linux/interrupt.h>
81 typedef irqreturn_t (*rtc_irq_handler)(int interrupt, void *cookie);
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/
Dcirrus,clps711x-intc.txt1 Cirrus Logic CLPS711X Interrupt Controller
5 - compatible: Should be "cirrus,ep7209-intc".
6 - reg: Specifies base physical address of the registers set.
7 - interrupt-controller: Identifies the node as an interrupt controller.
8 - #interrupt-cells: Specifies the number of cells needed to encode an
9 interrupt source. The value shall be 1.
11 The interrupt sources are as follows:
13 ---------------------------
30 18: SS2TX SSI2 transmit FIFO less than half empty
36 intc: interrupt-controller {
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/
Dcirrus,clps711x-intc.txt1 Cirrus Logic CLPS711X Interrupt Controller
5 - compatible: Should be "cirrus,ep7209-intc".
6 - reg: Specifies base physical address of the registers set.
7 - interrupt-controller: Identifies the node as an interrupt controller.
8 - #interrupt-cells: Specifies the number of cells needed to encode an
9 interrupt source. The value shall be 1.
11 The interrupt sources are as follows:
13 ---------------------------
30 18: SS2TX SSI2 transmit FIFO less than half empty
36 intc: interrupt-controller {
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/light/
Dti,opt3001.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andreas Dannenberg <dannenberg@ti.com>
13 The device supports interrupt-driven and interrupt-less operation, depending
14 on whether an interrupt property has been populated into the DT.
30 - compatible
31 - reg
34 - |
35 #include <dt-bindings/interrupt-controller/irq.h>
[all …]
/kernel/linux/linux-5.10/arch/x86/include/asm/
Dhpet.h1 /* SPDX-License-Identifier: GPL-2.0 */
59 * Min HPET period is 10^5 femto sec just for safety. If it is less than this,
60 * then 32 bit HPET counter wrapsaround in less than 0.5 sec.
90 #include <linux/interrupt.h>
92 typedef irqreturn_t (*rtc_irq_handler)(int interrupt, void *cookie);
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/memory-controllers/
Drockchip,rk3399-dmc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/rockchip,rk3399-dmc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Brian Norris <briannorris@chromium.org>
15 - rockchip,rk3399-dmc
17 devfreq-events:
21 Documentation/devicetree/bindings/devfreq/event/rockchip-dfi.txt.
26 clock-names:
28 - const: dmc_clk
[all …]
/kernel/linux/linux-6.6/include/linux/
Drbtree_latch.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Latched RB-trees
7 * Since RB-trees have non-atomic modifications they're not immediately suited
8 * for RCU/lockless queries. Even though we made RB-tree lookups non-fatal for
11 * The simplest solution is a seqlock + RB-tree, this will allow lockless
17 * employing the latch technique -- see @raw_write_seqcount_latch -- to
18 * implement a latched RB-tree which does allow for unconditional lookups by
26 * Therefore, this does require a lockless RB-tree iteration to be non-fatal;
28 * condition -- not seeing partial stores -- because the latch thing isolates
29 * us from loops. If we were to interrupt a modification the lookup would be
[all …]
/kernel/linux/linux-5.10/include/linux/
Drbtree_latch.h1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Latched RB-trees
7 * Since RB-trees have non-atomic modifications they're not immediately suited
8 * for RCU/lockless queries. Even though we made RB-tree lookups non-fatal for
11 * The simplest solution is a seqlock + RB-tree, this will allow lockless
17 * employing the latch technique -- see @raw_write_seqcount_latch -- to
18 * implement a latched RB-tree which does allow for unconditional lookups by
26 * Therefore, this does require a lockless RB-tree iteration to be non-fatal;
28 * condition -- not seeing partial stores -- because the latch thing isolates
29 * us from loops. If we were to interrupt a modification the lookup would be
[all …]
/kernel/linux/linux-6.6/drivers/misc/cxl/
Dhcalls.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
26 * The 'flags' parameter regroups the various bit-fields
59 * cxl_h_detach_process - Detach a process element from a coherent
65 * cxl_h_reset_afu - Perform a reset to the coherent platform function.
70 * cxl_h_suspend_process - Suspend a process from being executed
71 * Parameter1 = process-token as returned from H_ATTACH_CA_PROCESS when
77 * cxl_h_resume_process - Resume a process to be executed
78 * Parameter1 = process-token as returned from H_ATTACH_CA_PROCESS when
84 * cxl_h_read_error_state - Reads the error state of the coherent
91 * cxl_h_get_afu_err - collect the AFU error buffer
[all …]
/kernel/linux/linux-5.10/drivers/misc/cxl/
Dhcalls.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
26 * The 'flags' parameter regroups the various bit-fields
59 * cxl_h_detach_process - Detach a process element from a coherent
65 * cxl_h_reset_afu - Perform a reset to the coherent platform function.
70 * cxl_h_suspend_process - Suspend a process from being executed
71 * Parameter1 = process-token as returned from H_ATTACH_CA_PROCESS when
77 * cxl_h_resume_process - Resume a process to be executed
78 * Parameter1 = process-token as returned from H_ATTACH_CA_PROCESS when
84 * cxl_h_read_error_state - Reads the error state of the coherent
91 * cxl_h_get_afu_err - collect the AFU error buffer
[all …]
/kernel/linux/linux-5.10/Documentation/virt/kvm/
Dvcpu-requests.rst44 ----------
62 ---------
64 VCPUs have a mode state, ``vcpu->mode``, that is used to track whether the
66 outside guest mode states. The architecture may use ``vcpu->mode`` to
94 VCPU requests are simply bit indices of the ``vcpu->requests`` bitmap.
95 This means general bitops, like those documented in [atomic-ops]_ could
98 clear_bit(KVM_REQ_UNHALT & KVM_REQUEST_MASK, &vcpu->requests);
106 ---------------------------------
124 of a VCPU. It informs the VCPU thread to inject a timer interrupt.
132 event or interrupt arrives kvm_vcpu_block() makes the request. This is
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/can/
Dtcan4x5x.txt7 - compatible: "ti,tcan4x5x"
8 - reg: 0
9 - #address-cells: 1
10 - #size-cells: 0
11 - spi-max-frequency: Maximum frequency of the SPI bus the chip can
12 operate at should be less than or equal to 18 MHz.
13 - interrupt-parent: the phandle to the interrupt controller which provides
14 the interrupt.
15 - interrupts: interrupt specification for data-ready.
21 - reset-gpios: Hardwired output GPIO. If not defined then software
[all …]
/kernel/linux/linux-5.10/drivers/media/rc/img-ir/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
17 less reliable (due to lack of timestamps) and consumes more
26 signals in hardware. This is more reliable, consumes less processing
27 power since only a single interrupt is received for each scancode,
34 Say Y here to enable support for the NEC, extended NEC, and 32-bit
/kernel/linux/linux-6.6/drivers/media/rc/img-ir/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
17 less reliable (due to lack of timestamps) and consumes more
26 signals in hardware. This is more reliable, consumes less processing
27 power since only a single interrupt is received for each scancode,
35 Say Y here to enable support for the NEC, extended NEC, and 32-bit
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/can/
Dtcan4x5x.txt7 - compatible:
11 - reg: 0
12 - #address-cells: 1
13 - #size-cells: 0
14 - spi-max-frequency: Maximum frequency of the SPI bus the chip can
15 operate at should be less than or equal to 18 MHz.
16 - interrupt-parent: the phandle to the interrupt controller which provides
17 the interrupt.
18 - interrupts: interrupt specification for data-ready.
24 - reset-gpios: Hardwired output GPIO. If not defined then software
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/
Dfloppy.rst19 Example: If your kernel is called linux-2.6.9, type the following line
22 linux-2.6.9 floppy=thinkpad
25 of linux-2.6.9::
31 linux-2.6.9 floppy=daring floppy=two_fdc
96 and is thus harder to find, whereas non-dma buffers may be
104 If you have a FIFO-able FDC, the floppy driver automatically
105 falls back on non DMA mode if no DMA-able memory can be found.
123 interrupt latency, but it triggers more interrupts (i.e. it
125 lower, the interrupt latency should be lower too (faster
126 processor). The benefit of a lower threshold is less
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/blockdev/
Dfloppy.rst19 Example: If your kernel is called linux-2.6.9, type the following line
22 linux-2.6.9 floppy=thinkpad
25 of linux-2.6.9::
31 linux-2.6.9 floppy=daring floppy=two_fdc
96 and is thus harder to find, whereas non-dma buffers may be
104 If you have a FIFO-able FDC, the floppy driver automatically
105 falls back on non DMA mode if no DMA-able memory can be found.
123 interrupt latency, but it triggers more interrupts (i.e. it
125 lower, the interrupt latency should be lower too (faster
126 processor). The benefit of a lower threshold is less
[all …]

12345678910>>...41