Searched full:modeled (Results 1 – 25 of 66) sorted by relevance
123
| /kernel/linux/linux-5.10/tools/memory-model/Documentation/ |
| D | litmus-tests.txt | 60 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-5.10/include/linux/spi/ |
| D | mmc_spi.h | 12 * card slot. (Modeled after PXA mmc glue; see that for usage examples.)
|
| /kernel/linux/linux-5.10/drivers/media/usb/gspca/m5602/ |
| D | m5602_sensor.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_s5k83a.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_s5k4aa.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_ov7660.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_mt9m111.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_po1030.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_bridge.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_ov9650.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/ |
| D | simple-bridge.yaml | 35 This device has two video ports. Their connections are modeled using the
|
| D | thine,thc63lvd1024.yaml | 30 This device has four video ports. Their connections are modeled using the
|
| D | lvds-codec.yaml | 50 This device has two video ports. Their connections are modeled using the
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | truly,nt35597.txt | 21 are modeled using the OF graph bindings specified in
|
| D | arm,hdlcd.txt | 20 - port: The HDLCD connection to an encoder chip. The connection is modeled
|
| D | arm,komeda.txt | 28 modeled using the OF graph bindings specified in
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/rockchip/ |
| D | rockchip-lvds.txt | 33 Their connections are modeled using the OF graph bindings specified in
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,gsbi.txt | 3 The GSBI controller is modeled as a node with zero or more child nodes, each
|
| D | qcom,geni-se.yaml | 18 Wrapper controller is modeled as a node with zero or more child nodes each
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | tc3589x.txt | 46 keys. The linux-specific properties are modeled on those already existing
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/rcar-du/ |
| D | rcar_du_group.c | 16 * This would be modeled as two separate DU device instances if it wasn't for
19 * modeled as a single device with three CRTCs, two sets of "semi-global"
|
| /kernel/linux/linux-5.10/include/linux/mfd/ |
| D | ab3100.h | 72 * modeled as a separate regulator.
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/intel/iavf/ |
| D | iavf_trace.h | 4 /* Modeled on trace-events-sample.h */
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/intel/i40e/ |
| D | i40e_trace.h | 4 /* Modeled on trace-events-sample.h */
|
| /kernel/linux/linux-5.10/drivers/ide/ |
| D | delkin_cb.c | 6 * Modeled after the 16-bit PCMCIA driver: ide-cs.c
|
123