mipi_C-PHY_specification_v1-1_r05.pdf-FPGA CPLD资料源码分享社区-FPGA CPLD-ChipDebug

mipi_C-PHY_specification_v1-1_r05.pdf

该帖子部分内容已隐藏
付费阅读
10积分
10 Alliance application or protocol level specifications. This includes the physical interface, electrical interface, 11 low-level timing and the PHY-level protocol. The goal has been to define a C-PHY high-speed interface that 12 can coexist on the same pins as the MIPI D-PHY interface. These functional areas taken together are known 13 as C-PHY.

mipi_C-PHY_specification_v1-1_r05.pdf

• Specification of the PHY-Protocol Interface. The C-PHY specification includes a PHY-Protocol
47 Interface (PPI) annex that provides one possible solution for this interface. This annex is limited to
48 the essential signals for normal operation in order to clarify the kind of signals needed at this
49 interface. For power reasons this interface will be internal for most applications. Practical
50 implementations may be different without being inconsistent with the C-PHY specification.
51 • Implementations. This specification is intended to restrict the implementation as little as possible.
52 Various sections of this specification use block diagrams or example circuits to illustrate the
53 concept and are not in any way claimed to be the preferred or required implementation. Only the
54 behavior on the C-PHY interface pins is normative. Regulatory compliance methods are not within
55 the scope of this document. It is the responsibility of product manufacturers to ensure that their
56 designs comply with all applicable regulatory requirements.
57 The C-PHY Specification evolution is primarily driven by the need to achieve higher data rates and better
58 efficiency, while at the same time respecting backward compatibility. In this process the previous version of
59 the specification is taken and modifications are added, without compromising backward compatibility. Each
60 new version of the specification that is derived both preserves all the specification components of the previous
61 version, and adds the new changes. Due to technology evolution, some parameters are changed to optimize
62 for newer technologies.
63 It is recommended to always follow the latest version of the C-PHY Specification, irrespective of the targeted
64 data rate. The product data sheet should mention both the targeted C-PHY Specification version and data
65 rates. This will enable the system integrator to make proper decisions to achieve interoperability goals.
66 Items that are outside of the scope of this document are generally the same as those described in the D-PHY
67 specification, except for a detailed description of built-in test circuitry and test patterns. The built-in test
68 circuit description is included as an informative chapter to be followed at the option of the system or device
69 implementer. This document deviates from the norm and defines the behaviors of the test circuitry because
70 the general functionality of C-PHY is different from most other PHY implementations. It is useful to provide
71 a common test circuit description that can be followed by device implementers and test equipment providers
72 so there will be compatibility between devices implementing C-PHY and test equipment.
73 Coexistence with D-PHY on the same IC pins is possible, and likely in many applications; the means of doing
74 so is beyond the scope of this standard.
75 Regulatory compliance methods are not within the scope of this document. It is the responsibility of product
76 manufacturers to ensure that their designs comply with all applicable regulatory requirements.
1.2 Purpose
77 The C-PHY specification is used by manufacturers to design products that adhere to MIPI Alliance interface
78 specifications for mobile devices such as, but not limited to, camera, display and unified protocol interfaces.
79 Implementing this specification reduces the time-to-market and design cost of mobile devices by
80 standardizing the interface between products from different manufacturers. In addition, richer feature sets
81 requiring high data rates can be realized by implementing this specification. Finally, adding new features to
82 mobile devices is simplified due to the extensible nature of the MIPI Alliance Specifications.

请登录后发表评论

    没有回复内容