Home
last modified time | relevance | path

Searched full:unrelated (Results 1 – 25 of 282) sorted by relevance

12345678910>>...12

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/
Di2c-mux-gpmux.txt31 - mux-locked: If present, explicitly allow unrelated I2C transactions on the
42 This means that no unrelated I2C transactions are allowed on the parent I2C
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/
Di2c-mux-gpmux.yaml52 Explicitly allow unrelated I2C transactions on the parent I2C adapter at
64 This means that no unrelated I2C transactions are allowed on the parent I2C
/kernel/linux/linux-6.6/arch/s390/include/asm/
Ddma.h8 * MAX_DMA_ADDRESS is ambiguous because on s390 its completely unrelated
/kernel/linux/linux-5.10/arch/s390/include/asm/
Ddma.h8 * MAX_DMA_ADDRESS is ambiguous because on s390 its completely unrelated
/kernel/linux/linux-6.6/arch/arm/include/asm/
Dcache.h14 * unrelated code may cause parts of the buffer to be read into the
/kernel/linux/linux-5.10/arch/arm/include/asm/
Dcache.h14 * unrelated code may cause parts of the buffer to be read into the
/kernel/linux/linux-6.6/drivers/staging/fieldbus/anybuss/
DKconfig22 There is also a CAN power readout, unrelated to the Anybus,
/kernel/linux/linux-5.10/drivers/staging/fieldbus/anybuss/
DKconfig22 There is also a CAN power readout, unrelated to the Anybus,
/kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/
Dmedia-controller-intro.rst25 between seemingly unrelated devices.
/kernel/linux/linux-6.6/Documentation/userspace-api/media/mediactl/
Dmedia-controller-intro.rst25 between seemingly unrelated devices.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/
Dnxp,sysctr-timer.yaml16 is always powered and support multiple, unrelated clocks. The
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/timer/
Dnxp,sysctr-timer.yaml16 is always powered and support multiple, unrelated clocks. The
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dmfd.txt16 mix of unrelated hardware devices.
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/
Dmfd.txt16 mix of unrelated hardware devices.
/kernel/linux/linux-6.6/tools/testing/selftests/arm64/signal/
Dsignals.S45 * for unrelated reasons, so we should consider the possibly observed
/kernel/linux/linux-5.10/scripts/coccinelle/misc/
Duninitialized_var.cocci7 /// papers over real bugs (or can in the future), and suppresses unrelated
/kernel/linux/linux-5.10/tools/testing/selftests/arm64/signal/
Dsignals.S45 * for unrelated reasons, so we should consider the possibly observed
/kernel/linux/linux-6.6/Documentation/firmware-guide/acpi/
Dosi.rst57 completely unrelated code on completely unrelated systems. This prompted
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dreporting-bugs.rst82 It's REALLY important to report bugs that seem unrelated as separate email
83 threads or separate bugzilla entries. If you report several unrelated
/kernel/linux/linux-6.6/scripts/coccinelle/misc/
Duninitialized_var.cocci9 /// papers over real bugs (or can in the future), and suppresses unrelated
/kernel/linux/linux-5.10/Documentation/misc-devices/
Dad525x_dpot.rst38 address of 0x2f, we descend (unrelated sysfs entries have been trimmed)::
/kernel/linux/linux-6.6/Documentation/misc-devices/
Dad525x_dpot.rst38 address of 0x2f, we descend (unrelated sysfs entries have been trimmed)::
/kernel/linux/linux-5.10/arch/arm/kernel/
Dio.c12 * Allows thread-safe access to registers shared by unrelated subsystems.
/kernel/linux/linux-6.6/arch/arm/kernel/
Dio.c12 * Allows thread-safe access to registers shared by unrelated subsystems.
/kernel/linux/linux-6.6/drivers/gpu/drm/i915/gt/
Dintel_gt_mcr.h52 * slice/subslice topology. On Xe_HP and beyond, the steering is unrelated to

12345678910>>...12