Home
last modified time | relevance | path

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

123

/Linux-v5.15/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,
969 3. Exceptions and interrupts are not modeled. In some cases,
991 b. The "unless" RMW operations are not currently modeled:
999 modeled by herd7 therefore it can be used in litmus tests.
1001 c. The call_rcu() function is not modeled. As was shown above,
1008 d. The rcu_barrier() function is not modeled. It can be
1014 e. Although sleepable RCU (SRCU) is now modeled, there
1039 f. Reader-writer locking is not modeled. It can be
/Linux-v5.15/include/linux/spi/
Dmmc_spi.h12 * card slot. (Modeled after PXA mmc glue; see that for usage examples.)
/Linux-v5.15/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_ov7660.h11 * v4l2 interface modeled after the V4L2 driver
Dm5602_s5k4aa.h11 * v4l2 interface modeled after the V4L2 driver
Dm5602_mt9m111.h11 * v4l2 interface modeled after the V4L2 driver
Dm5602_po1030.h11 * v4l2 interface modeled after the V4L2 driver
Dm5602_bridge.h11 * v4l2 interface modeled after the V4L2 driver
Dm5602_ov9650.h11 * v4l2 interface modeled after the V4L2 driver
/Linux-v5.15/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
/Linux-v5.15/Documentation/devicetree/bindings/display/rockchip/
Drockchip-lvds.txt33 Their connections are modeled using the OF graph bindings specified in
/Linux-v5.15/Documentation/devicetree/bindings/soc/qcom/
Dqcom,gsbi.txt3 The GSBI controller is modeled as a node with zero or more child nodes, each
Dqcom,geni-se.yaml18 Wrapper controller is modeled as a node with zero or more child nodes each
/Linux-v5.15/Documentation/devicetree/bindings/mfd/
Dtc3589x.txt46 keys. The linux-specific properties are modeled on those already existing
/Linux-v5.15/drivers/gpu/drm/rcar-du/
Drcar_du_group.c16 * 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-v5.15/drivers/net/ethernet/intel/iavf/
Diavf_trace.h4 /* Modeled on trace-events-sample.h */
/Linux-v5.15/include/uapi/linux/
Drtc.h50 * This is modeled after the RTC used in Q40/Q60 computers but
/Linux-v5.15/drivers/net/ethernet/intel/i40e/
Di40e_trace.h4 /* Modeled on trace-events-sample.h */
/Linux-v5.15/drivers/net/wireless/intersil/orinoco/
Dorinoco_tmd.c33 * This driver is modeled after the orinoco_plx driver. The main
/Linux-v5.15/drivers/net/ethernet/intel/ice/
Dice_trace.h4 /* Modeled on trace-events-sample.h */
/Linux-v5.15/Documentation/PCI/endpoint/
Dpci-ntb-function.rst228 scratchpad, doorbell, one or more memory windows) to be modeled to achieve
347 This is modeled the same was as MW1 but each of the additional memory windows
/Linux-v5.15/drivers/media/rc/
Dnuvoton-cir.h11 * modeled after.

123