Searched full:diagram (Results 1 – 25 of 231) sorted by relevance
12345678910
| /linux-6.12.1/Documentation/devicetree/bindings/phy/ |
| D | hisilicon,hi3660-usb3.yaml | 29 hisilicon,eye-diagram-param:
32 description: Eye diagram for phy.
38 - hisilicon,eye-diagram-param
50 hisilicon,eye-diagram-param = <0x22466e4>;
|
| D | hisilicon,hi3670-usb3.yaml | 34 hisilicon,eye-diagram-param:
37 description: Eye diagram for phy.
48 - hisilicon,eye-diagram-param
62 hisilicon,eye-diagram-param = <0xfdfee4>;
|
| D | hisilicon,phy-hi3670-pcie.yaml | 45 hisilicon,eye-diagram-param:
47 description: Eye diagram for phy.
55 - hisilicon,eye-diagram-param
79 hisilicon,eye-diagram-param = <0xffffffff 0xffffffff
|
| D | qcom,usb-hs-phy.yaml | 80 This is related to Device Mode Eye Diagram test.
|
| /linux-6.12.1/Documentation/devicetree/bindings/display/panel/ |
| D | panel-edp.yaml | 37 vast majority of panel datasheets have a power sequence diagram that
39 cares about different timings in this diagram but the fact that the
40 diagram is so similar means we can come up with a single driver to
45 sequence. This is because much of this diagram comes straight from
102 from power on (timing T3 in the diagram above). If we have no way to
|
| /linux-6.12.1/Documentation/gpu/amdgpu/display/ |
| D | dcn-overview.rst | 8 generic diagram, and we have variations per ASIC.
12 Based on this diagram, we can pass through each block and briefly describe
51 The above diagram is an architecture generalization of DCN, which means that
62 sophisticated communication interface which is highlighted in the diagram by
158 The first thing to notice from the diagram and DTN log it is the fact that we
162 we can split this single pipe differently, as described in the below diagram:
|
| /linux-6.12.1/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 286 diagram above.
360 The diagram below shows the path of ordering if the leftmost
371 in the following diagram.
411 following diagram:
426 diagram happens after the start of the grace period. In addition, this
463 diagram, clearing bits from each ``rcu_node`` structure's ``->qsmask``
493 precede the idle period (the oval near the top of the diagram above)
497 the bottom of the diagram above).
556 | RCU. But this diagram is complex enough as it is, so simplicity |
559 | `stitched-together diagram <Putting It All Together_>`__. |
[all …]
|
| /linux-6.12.1/drivers/clk/rockchip/ |
| D | clk-rv1126.c | 269 * Clock-Architecture Diagram 2
392 * Clock-Architecture Diagram 1
399 * Clock-Architecture Diagram 3
416 * Clock-Architecture Diagram 4
626 * Clock-Architecture Diagram 6
723 * Clock-Architecture Diagram 9
766 * Clock-Architecture Diagram 12
888 * Clock-Architecture Diagram 15
904 * Clock-Architecture Diagram 3
919 * Clock-Architecture Diagram 4
[all …]
|
| D | clk-rk3328.c | 266 * Clock-Architecture Diagram 1
282 * Clock-Architecture Diagram 2
345 * Clock-Architecture Diagram 3
438 * Clock-Architecture Diagram 4
496 * Clock-Architecture Diagram 5
565 * Clock-Architecture Diagram 6
602 * Clock-Architecture Diagram 7
654 * Clock-Architecture Diagram 8
700 * Clock-Architecture Diagram 9
|
| D | clk-px30.c | 266 * Clock-Architecture Diagram 1
274 * Clock-Architecture Diagram 3
328 * Clock-Architecture Diagram 4
380 * Clock-Architecture Diagram 5
402 * Clock-Architecture Diagram 6
453 * Clock-Architecture Diagram 7
570 * Clock-Architecture Diagram 8
793 * Clock-Architecture Diagram 9
916 * Clock-Architecture Diagram 2
966 * Clock-Architecture Diagram 9
|
| D | clk-rk3308.c | 281 * Clock-Architecture Diagram 1
289 * Clock-Architecture Diagram 2
312 * Clock-Architecture Diagram 3
461 * Clock-Architecture Diagram 4
549 * Clock-Architecture Diagram 5
576 * Clock-Architecture Diagram 6
618 * Clock-Architecture Diagram 7
806 * Clock-Architecture Diagram 8
|
| /linux-6.12.1/Documentation/driver-api/pldmfw/ |
| D | file-format.rst | 12 This diagram provides an overview of the file format::
57 The following diagram provides an overview of the package header::
90 The following diagram provides an overview of the device record area::
145 The following diagram provides an overview of the component area::
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | interconnect.rst | 22 Below is a simplified diagram of a real-world SoC interconnect bus topology.
56 The interconnect providers on the above diagram are M NoC, S NoC, C NoC, P NoC
62 providers. The point on the diagram where the CPUs connect to the memory is
|
| /linux-6.12.1/Documentation/devicetree/bindings/net/ |
| D | hisilicon-hns-nic.txt | 17 port-id can be 2 to 7. Here is the diagram:
44 to the CPU. The port-idx-in-ae can be 0 to 5. Here is the diagram:
|
| /linux-6.12.1/Documentation/devicetree/bindings/pinctrl/ |
| D | starfive,jh7100-pinctrl.yaml | 15 interesting 2-layered approach to pin muxing best illustrated by the diagram
36 The big MUX in the diagram only has 7 different ways of mapping peripherals
40 diagram only shows UART0 and UART1, but this also includes a number of other
|
| /linux-6.12.1/Documentation/scsi/scsi_transport_srp/ |
| D | figures.rst | 3 SCSI RDMA (SRP) transport class diagram
|
| /linux-6.12.1/include/uapi/linux/ |
| D | ethtool.h | 976 * indicates that the PSE State diagram is in the state DISABLED.
978 * indicates the PSE State diagram is in a state other than those
981 * "deliveringPower" indicates that the PSE State diagram is in the
984 * the PSE State diagram is in the state TEST_MODE.
986 * the PSE State diagram is in the state TEST_ERROR.
988 * indicates that the PSE State diagram is in the state IDLE due to
1020 * asserted true when the PoDL PSE state diagram variable mr_pse_enable is
1023 * asserted true when either of the PSE state diagram variables
1026 * is asserted true when the PoDL PSE state diagram variable pi_powered is
1029 * true when the PoDL PSE state diagram variable pi_sleeping is true."
[all …]
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | overview.rst | 31 The diagram below shows an overview of the DPAA2 resource management
84 types of DPAA2 objects. In the example diagram below there
144 The diagram below shows the objects needed for a simple
284 The diagram below shows the Linux drivers involved in a networking
|
| /linux-6.12.1/Documentation/devicetree/bindings/soc/hisilicon/ |
| D | hisilicon,hi3660-usb3-otg-bc.yaml | 44 hisilicon,eye-diagram-param = <0x22466e4>;
|
| /linux-6.12.1/drivers/gpu/drm/bridge/ |
| D | simple-bridge.c | 231 /* From timing diagram, datasheet page 9 */
244 /* From timing diagram, datasheet page 14 */
|
| /linux-6.12.1/Documentation/PCI/endpoint/ |
| D | pci-ntb-function.rst | 20 In the below diagram, PCI NTB function configures the SoC with multiple
291 Above diagram shows Config region + Scratchpad region for HOST1 (connected to
296 diagram shows the case where Config region and Scratchpad regions are allocated
335 Above diagram shows how the doorbell and memory window 1 is mapped so that
|
| /linux-6.12.1/Documentation/infiniband/ |
| D | opa_vnic.rst | 23 different virtual Ethernet switch. The below diagram presents a case
103 Intel OPA VNIC software design is presented in the below diagram.
|
| /linux-6.12.1/drivers/interconnect/imx/ |
| D | imx8mn.c | 29 * This is a simplified subset of the bus diagram, there are several other
|
| /linux-6.12.1/Documentation/networking/ |
| D | mac80211-auth-assoc-deauth.txt | 5 # This can be converted into a diagram using the service
|
| /linux-6.12.1/Documentation/bpf/ |
| D | map_hash.rst | 240 This algorithm is described visually in the following diagram. See the
245 :alt: Diagram outlining the LRU eviction steps taken during map update.
|
12345678910