| /linux/tools/memory-model/scripts/ |
| H A D | judgelitmus.sh | 69 echo '!!! Predicted data race not modeled' $litmus
74 echo '!!! Unexpected data race modeled' $litmus
|
| /linux/tools/memory-model/Documentation/ |
| H A 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,
986 3. Exceptions and interrupts are not modeled. In some cases,
1008 b. The "unless" RMW operations are not currently modeled:
1016 modeled by herd7 therefore it can be used in litmus tests.
1018 c. The call_rcu() function is not modeled. As was shown above,
1025 d. The rcu_barrier() function is not modeled. It can be
1031 e. Reader-writer locking is not modeled. It can be
|
| /linux/Documentation/devicetree/bindings/platform/ |
| H A D | microsoft,surface-sam.yaml | 15 specific functionalities are modeled as subdevices and matched on
|
| /linux/drivers/net/ethernet/intel/e1000e/ |
| H A D | e1000e_trace.h | 3 /* Modeled on trace-events-sample.h */
|
| /linux/include/linux/spi/ |
| H A D | mmc_spi.h | 12 * card slot. (Modeled after PXA mmc glue; see that for usage examples.)
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | usb-nop-xceiv.yaml | 43 GPIO line, this should be modeled as a regulator-fixed and
|
| /linux/drivers/media/usb/gspca/m5602/ |
| H A D | m5602_s5k83a.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| H A D | m5602_sensor.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| H A D | m5602_ov7660.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| H A D | m5602_s5k4aa.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| H A D | m5602_mt9m111.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| H A D | m5602_po1030.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| H A D | m5602_ov9650.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| H A D | m5602_bridge.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| /linux/Documentation/litmus-tests/ |
| H A D | README | 57 would be excluded by other code not modeled in the litmus test.
|
| /linux/Documentation/mm/ |
| H A D | multigen_lru.rst | 104 modeled after the PID controller monitors refaults over all the tiers
213 A feedback loop modeled after the Proportional-Integral-Derivative
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | tc3589x.txt | 46 keys. The linux-specific properties are modeled on those already existing
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | renesas,rzg2l-du.yaml | 55 The connections to the DU output video ports are modeled using the OF
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | samsung,exynos990-clock.yaml | 16 clocks for different domains. Those CMU units are modeled as separate device
|
| H A D | google,gs101-clock.yaml | 14 clocks for different domains. Those CMU units are modeled as separate device
|
| H A D | samsung,exynos7885-clock.yaml | 18 clocks for different domains. Those CMU units are modeled as separate device
|
| /linux/drivers/gpu/drm/renesas/rcar-du/ |
| H A 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"
|
| /linux/Documentation/devicetree/bindings/soc/qcom/ |
| H A D | qcom,gsbi.yaml | 15 The GSBI controller is modeled as a node with zero or more child nodes, each
|
| H A D | qcom,geni-se.yaml | 17 Wrapper controller is modeled as a node with zero or more child nodes each
|
| /linux/Documentation/devicetree/bindings/soc/samsung/ |
| H A D | exynos-usi.yaml | 26 selected configuration is active at any given time. USI is modeled as a node
|