Searched full:diagram (Results 1 – 25 of 383) sorted by relevance
12345678910>>...16
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | hisilicon,hi3660-usb3.yaml | 29 hisilicon,eye-diagram-param:
31 description: Eye diagram for phy.
37 - hisilicon,eye-diagram-param
57 hisilicon,eye-diagram-param = <0x22466e4>;
|
| /kernel/linux/linux-5.10/drivers/staging/hikey9xx/ |
| D | phy-hi3670-usb3.yaml | 33 hisilicon,eye-diagram-param:
35 description: Eye diagram for phy.
46 - hisilicon,eye-diagram-param
68 hisilicon,eye-diagram-param = <0xfdfee4>;
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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:
|
| /kernel/linux/linux-5.10/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 262 diagram above.
336 The diagram below shows the path of ordering if the leftmost
347 in the following diagram.
387 following diagram:
402 diagram happens after the start of the grace period. In addition, this
439 diagram, clearing bits from each ``rcu_node`` structure's ``->qsmask``
469 precede the idle period (the oval near the top of the diagram above)
473 the bottom of the diagram above).
532 | RCU. But this diagram is complex enough as it is, so simplicity |
535 | `stitched-together diagram <#Putting%20It%20All%20Together>`__. |
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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::
|
| /kernel/linux/linux-5.10/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::
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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:
|
| /kernel/linux/linux-5.10/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:
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/drivers/phy/ti/ |
| D | phy-tusb1210.c | 35 /* Restore the optional eye diagram optimization value */ in tusb1210_power_on()
118 * diagram optimization and DP/DM swap. in tusb1210_probe()
|
| /kernel/linux/linux-5.10/Documentation/scsi/scsi_transport_srp/ |
| D | figures.rst | 3 SCSI RDMA (SRP) transport class diagram
|
| /kernel/linux/linux-6.6/Documentation/scsi/scsi_transport_srp/ |
| D | figures.rst | 3 SCSI RDMA (SRP) transport class diagram
|
| /kernel/linux/linux-5.10/drivers/clk/rockchip/ |
| D | clk-rk3328.c | 265 * Clock-Architecture Diagram 1
281 * Clock-Architecture Diagram 2
344 * Clock-Architecture Diagram 3
437 * Clock-Architecture Diagram 4
495 * Clock-Architecture Diagram 5
564 * Clock-Architecture Diagram 6
601 * Clock-Architecture Diagram 7
653 * Clock-Architecture Diagram 8
699 * Clock-Architecture Diagram 9
|
| D | clk-px30.c | 265 * Clock-Architecture Diagram 1
273 * Clock-Architecture Diagram 3
327 * Clock-Architecture Diagram 4
379 * Clock-Architecture Diagram 5
401 * Clock-Architecture Diagram 6
452 * Clock-Architecture Diagram 7
569 * Clock-Architecture Diagram 8
792 * Clock-Architecture Diagram 9
915 * Clock-Architecture Diagram 2
965 * Clock-Architecture Diagram 9
|
| /kernel/linux/linux-5.10/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
283 The diagram below shows the Linux drivers involved in a networking
|
12345678910>>...16