Home
last modified time | relevance | path

Searched full:modeled (Results 1 – 25 of 133) sorted by relevance

123456

/kernel/linux/linux-5.10/tools/memory-model/Documentation/
Dlitmus-tests.txt60 appears often in the Linux kernel. For example, a flag (modeled by "y"
61 below) indicates that a buffer (modeled by "x" below) is now completely
935 1. Compiler optimizations are not accurately modeled. Of course,
952 3. Exceptions and interrupts are not modeled. In some cases,
974 b. The "unless" RMW operations are not currently modeled:
982 modeled by herd7 therefore it can be used in litmus tests.
984 c. The call_rcu() function is not modeled. As was shown above,
991 d. The rcu_barrier() function is not modeled. It can be
997 e. Although sleepable RCU (SRCU) is now modeled, there
1022 f. Reader-writer locking is not modeled. It can be
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/connector/
Dvga-connector.txt15 The VGA connector internal connections are modeled using the OF graph bindings
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/bridge/
Dadi,adv7123.txt17 The ADV7123 has two video ports. Their connections are modeled using the OF
Dthine,thc63lvdm83d.txt17 The THC63LVDM83D has two video ports. Their connections are modeled using the
Dlvds-transmitter.txt29 This device has two video ports. Their connections are modeled using the OF
Dthine,thc63lvd1024.txt20 The THC63LVD1024 video port connections are modeled according
/kernel/linux/linux-4.19/tools/memory-model/
DREADME166 1. Compiler optimizations are not modeled. Of course, the use
177 3. Exceptions and interrupts are not modeled. In some cases,
/kernel/linux/linux-5.10/include/linux/spi/
Dmmc_spi.h12 * card slot. (Modeled after PXA mmc glue; see that for usage examples.)
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/connector/
Dsamsung,usb-connector-11pin.txt15 - any data bus to the connector should be modeled using the OF graph bindings
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/
Dsimple-bridge.yaml35 This device has two video ports. Their connections are modeled using the
/kernel/linux/linux-5.10/drivers/media/usb/gspca/m5602/
Dm5602_s5k83a.h11 * v4l2 interface modeled after the V4L2 driver
Dm5602_sensor.h11 * v4l2 interface modeled after the V4L2 driver
Dm5602_s5k4aa.h11 * v4l2 interface modeled after the V4L2 driver
Dm5602_ov7660.h11 * v4l2 interface modeled after the V4L2 driver
/kernel/linux/linux-4.19/drivers/media/usb/gspca/m5602/
Dm5602_sensor.h10 * v4l2 interface modeled after the V4L2 driver
Dm5602_s5k83a.h10 * v4l2 interface modeled after the V4L2 driver
Dm5602_ov7660.h10 * v4l2 interface modeled after the V4L2 driver
/kernel/linux/linux-4.19/include/linux/spi/
Dmmc_spi.h17 * card slot. (Modeled after PXA mmc glue; see that for usage examples.)
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/
Dtruly,nt35597.txt21 are modeled using the OF graph bindings specified in
Darm,hdlcd.txt20 - port: The HDLCD connection to an encoder chip. The connection is modeled
Darm,komeda.txt28 modeled using the OF graph bindings specified in
/kernel/linux/linux-4.19/drivers/gpu/drm/rcar-du/
Drcar_du_group.c20 * This would be modeled as two separate DU device instances if it wasn't for
23 * modeled as a single device with three CRTCs, two sets of "semi-global"
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/
Darm,hdlcd.txt20 - port: The HDLCD connection to an encoder chip. The connection is modeled
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/media/
Drenesas,ceu.txt18 subnode with a single 'endpoint'. Connection to input devices are modeled
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/rockchip/
Drockchip-lvds.txt33 Their connections are modeled using the OF graph bindings specified in

123456