Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  1) ====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  2) Xilinx Zynq MPSoC EEMI Documentation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  3) ====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  4) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  5) Xilinx Zynq MPSoC Firmware Interface
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  6) -------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  7) The zynqmp-firmware node describes the interface to platform firmware.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  8) ZynqMP has an interface to communicate with secure firmware. Firmware
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  9) driver provides an interface to firmware APIs. Interface APIs can be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) used by any driver to communicate with PMC(Platform Management Controller).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) Embedded Energy Management Interface (EEMI)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) ----------------------------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) The embedded energy management interface is used to allow software
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) components running across different processing clusters on a chip or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) device to communicate with a power management controller (PMC) on a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) device to issue or respond to power management requests.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) Any driver who wants to communicate with PMC using EEMI APIs use the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) functions provided for each function.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) IOCTL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) ------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) IOCTL API is for device control and configuration. It is not a system
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) IOCTL but it is an EEMI API. This API can be used by master to control
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) any device specific configuration. IOCTL definitions can be platform
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) specific. This API also manage shared device configuration.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) The following IOCTL IDs are valid for device control:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) - IOCTL_SET_PLL_FRAC_MODE	8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) - IOCTL_GET_PLL_FRAC_MODE	9
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) - IOCTL_SET_PLL_FRAC_DATA	10
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) - IOCTL_GET_PLL_FRAC_DATA	11
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) Refer EEMI API guide [0] for IOCTL specific parameters and other EEMI APIs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) References
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) ----------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) [0] Embedded Energy Management Interface (EEMI) API guide:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40)     https://www.xilinx.com/support/documentation/user_guides/ug1200-eemi-api.pdf