Searched full:modeled (Results 1 – 25 of 28) sorted by relevance
12
| /Documentation/devicetree/bindings/platform/ |
| D | microsoft,surface-sam.yaml | 15 specific functionalities are modeled as subdevices and matched on
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-nop-xceiv.yaml | 43 GPIO line, this should be modeled as a regulator-fixed and
|
| /Documentation/devicetree/bindings/display/ |
| D | truly,nt35597.txt | 21 are modeled using the OF graph bindings specified in
|
| D | renesas,rzg2l-du.yaml | 55 The connections to the DU output video ports are modeled using the OF
|
| D | renesas,du.yaml | 62 The connections to the DU output video ports are modeled using the OF
|
| /Documentation/litmus-tests/ |
| D | README | 57 would be excluded by other code not modeled in the litmus test.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | tc3589x.txt | 46 keys. The linux-specific properties are modeled on those already existing
|
| /Documentation/devicetree/bindings/clock/ |
| D | samsung,exynosautov920-clock.yaml | 17 clocks for different domains. Those CMU units are modeled as separate device
|
| D | google,gs101-clock.yaml | 14 clocks for different domains. Those CMU units are modeled as separate device
|
| D | samsung,exynos7885-clock.yaml | 18 clocks for different domains. Those CMU units are modeled as separate device
|
| D | samsung,exynosautov9-clock.yaml | 18 clocks for different domains. Those CMU units are modeled as separate device
|
| D | samsung,exynos850-clock.yaml | 18 clocks for different domains. Those CMU units are modeled as separate device
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,gsbi.yaml | 15 The GSBI controller is modeled as a node with zero or more child nodes, each
|
| D | qcom,geni-se.yaml | 17 Wrapper controller is modeled as a node with zero or more child nodes each
|
| /Documentation/virt/hyperv/ |
| D | vmbus.rst | 15 VMBus is modeled in Linux as a bus, with the expected /sys/bus/vmbus
179 they are best modeled in Linux as per-CPU interrupts. This model works
193 The synic is not modeled in Linux as an irq chip or irq domain,
|
| /Documentation/devicetree/bindings/soc/samsung/ |
| D | exynos-usi.yaml | 16 protocol can be chosen at a time. USI is modeled as a node with zero or more
|
| /Documentation/mm/ |
| 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
|
| /Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 46 modeled as a graph of match/action tables. Each table represents a specific
|
| /Documentation/PCI/endpoint/ |
| D | pci-ntb-function.rst | 228 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
|
| /Documentation/networking/ |
| D | can_ucan_protocol.rst | 10 It is modeled closely after how Linux represents CAN devices
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-controller.yaml | 309 be modeled as a "regulator-fixed" with a GPIO line for
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 639 The sensors, the bridge and the receiver are modeled as V4L2 sub-devices,
641 modeled as V4L2 devices, exposed to userspace via /dev/videoX nodes.
|
| /Documentation/bpf/ |
| D | classic_vs_extended.rst | 338 and perform function exit. eBPF is modeled to match CPU, so BPF_JMP | BPF_EXIT
|
| /Documentation/dev-tools/ |
| D | kcsan.rst | 324 means reordering of marked accesses is not modeled.
|
| /Documentation/networking/dsa/ |
| D | sja1105.rst | 399 accessed through SPI commands, modeled in Linux as virtual MDIO buses.
|
12