Home
last modified time | relevance | path

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

12345

/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
/linux-5.10/arch/s390/include/asm/
Ddma.h8 * MAX_DMA_ADDRESS is ambiguous because on s390 its completely unrelated
/linux-5.10/arch/arm/include/asm/
Dcache.h14 * unrelated code may cause parts of the buffer to be read into the
/linux-5.10/drivers/staging/fieldbus/anybuss/
DKconfig22 There is also a CAN power readout, unrelated to the Anybus,
/linux-5.10/Documentation/userspace-api/media/mediactl/
Dmedia-controller-intro.rst25 between seemingly unrelated devices.
/linux-5.10/Documentation/devicetree/bindings/timer/
Dnxp,sysctr-timer.yaml16 is always powered and support multiple, unrelated clocks. The
/linux-5.10/Documentation/devicetree/bindings/mfd/
Dmfd.txt16 mix of unrelated hardware devices.
/linux-5.10/tools/testing/selftests/arm64/signal/
Dsignals.S45 * for unrelated reasons, so we should consider the possibly observed
DREADME39 unrelated SEGV bugs in the testcases, it becomes extremely tricky to
/linux-5.10/scripts/coccinelle/misc/
Duninitialized_var.cocci7 /// papers over real bugs (or can in the future), and suppresses unrelated
/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
/linux-5.10/Documentation/misc-devices/
Dad525x_dpot.rst38 address of 0x2f, we descend (unrelated sysfs entries have been trimmed)::
/linux-5.10/arch/arm/kernel/
Dio.c12 * Allows thread-safe access to registers shared by unrelated subsystems.
/linux-5.10/fs/xfs/
Dxfs_extfree_item.h40 * unrelated failure.
/linux-5.10/sound/
DKconfig113 sound subsystem and other function drivers completely unrelated to
/linux-5.10/net/unix/
Dgarbage.c48 * in unrelated processes.
63 * wrt receive and holding up unrelated socket operations.
/linux-5.10/Documentation/driver-api/iio/
Dtriggers.rst19 sensors and also it may be completely unrelated to the sensor itself.
/linux-5.10/include/media/
Dvideobuf-dma-sg.h81 * Despite the name, this is totally unrelated to videobuf, except that
/linux-5.10/Documentation/devicetree/bindings/reset/
Dreset.txt23 the DT node of each affected HW block, since if activated, an unrelated block
/linux-5.10/arch/arm64/include/asm/
Dcache.h46 * unrelated code may cause parts of the buffer to be read into the
/linux-5.10/Documentation/i2c/
Di2c-topology.rst88 full transaction, unrelated I2C transfers may interleave the different
112 number (one, in most cases) of I2C transfers. Unrelated I2C transfers
118 behind the mux, when an unrelated I2C transfer is in flight during
/linux-5.10/Documentation/admin-guide/cgroup-v1/
Dfreezer-subsystem.rst38 From a second, unrelated bash shell:
/linux-5.10/Documentation/ABI/testing/
Ddev-kmsg113 interleaved with unrelated messages, but merging the lines in
/linux-5.10/security/selinux/include/
Davc.h78 * permission. Take notice that this is unrelated to the in avc_audit_required()
/linux-5.10/Documentation/target/
Dtcmu-design.rst214 Other devices may be using UIO besides TCMU. Unrelated user processes
300 TCMU is designed so that multiple unrelated processes can manage TCMU

12345