~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/driver-api/xilinx/eemi.rst

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

Diff markup

Differences between /Documentation/driver-api/xilinx/eemi.rst (Version linux-6.12-rc7) and /Documentation/driver-api/xilinx/eemi.rst (Version linux-5.4.285)


  1 ====================================                1 ====================================
  2 Xilinx Zynq MPSoC EEMI Documentation                2 Xilinx Zynq MPSoC EEMI Documentation
  3 ====================================                3 ====================================
  4                                                     4 
  5 Xilinx Zynq MPSoC Firmware Interface                5 Xilinx Zynq MPSoC Firmware Interface
  6 -------------------------------------               6 -------------------------------------
  7 The zynqmp-firmware node describes the interfa      7 The zynqmp-firmware node describes the interface to platform firmware.
  8 ZynqMP has an interface to communicate with se      8 ZynqMP has an interface to communicate with secure firmware. Firmware
  9 driver provides an interface to firmware APIs.      9 driver provides an interface to firmware APIs. Interface APIs can be
 10 used by any driver to communicate with PMC(Pla     10 used by any driver to communicate with PMC(Platform Management Controller).
 11                                                    11 
 12 Embedded Energy Management Interface (EEMI)        12 Embedded Energy Management Interface (EEMI)
 13 ----------------------------------------------     13 ----------------------------------------------
 14 The embedded energy management interface is us     14 The embedded energy management interface is used to allow software
 15 components running across different processing     15 components running across different processing clusters on a chip or
 16 device to communicate with a power management      16 device to communicate with a power management controller (PMC) on a
 17 device to issue or respond to power management     17 device to issue or respond to power management requests.
 18                                                    18 
 19 Any driver who wants to communicate with PMC u !!  19 EEMI ops is a structure containing all eemi APIs supported by Zynq MPSoC.
 20 functions provided for each function.          !!  20 The zynqmp-firmware driver maintain all EEMI APIs in zynqmp_eemi_ops
                                                   >>  21 structure. Any driver who want to communicate with PMC using EEMI APIs
                                                   >>  22 can call zynqmp_pm_get_eemi_ops().
                                                   >>  23 
                                                   >>  24 Example of EEMI ops::
                                                   >>  25 
                                                   >>  26         /* zynqmp-firmware driver maintain all EEMI APIs */
                                                   >>  27         struct zynqmp_eemi_ops {
                                                   >>  28                 int (*get_api_version)(u32 *version);
                                                   >>  29                 int (*query_data)(struct zynqmp_pm_query_data qdata, u32 *out);
                                                   >>  30         };
                                                   >>  31 
                                                   >>  32         static const struct zynqmp_eemi_ops eemi_ops = {
                                                   >>  33                 .get_api_version = zynqmp_pm_get_api_version,
                                                   >>  34                 .query_data = zynqmp_pm_query_data,
                                                   >>  35         };
                                                   >>  36 
                                                   >>  37 Example of EEMI ops usage::
                                                   >>  38 
                                                   >>  39         static const struct zynqmp_eemi_ops *eemi_ops;
                                                   >>  40         u32 ret_payload[PAYLOAD_ARG_CNT];
                                                   >>  41         int ret;
                                                   >>  42 
                                                   >>  43         eemi_ops = zynqmp_pm_get_eemi_ops();
                                                   >>  44         if (IS_ERR(eemi_ops))
                                                   >>  45                 return PTR_ERR(eemi_ops);
                                                   >>  46 
                                                   >>  47         ret = eemi_ops->query_data(qdata, ret_payload);
 21                                                    48 
 22 IOCTL                                              49 IOCTL
 23 ------                                             50 ------
 24 IOCTL API is for device control and configurat     51 IOCTL API is for device control and configuration. It is not a system
 25 IOCTL but it is an EEMI API. This API can be u     52 IOCTL but it is an EEMI API. This API can be used by master to control
 26 any device specific configuration. IOCTL defin     53 any device specific configuration. IOCTL definitions can be platform
 27 specific. This API also manage shared device c     54 specific. This API also manage shared device configuration.
 28                                                    55 
 29 The following IOCTL IDs are valid for device c     56 The following IOCTL IDs are valid for device control:
 30 - IOCTL_SET_PLL_FRAC_MODE       8                  57 - IOCTL_SET_PLL_FRAC_MODE       8
 31 - IOCTL_GET_PLL_FRAC_MODE       9                  58 - IOCTL_GET_PLL_FRAC_MODE       9
 32 - IOCTL_SET_PLL_FRAC_DATA       10                 59 - IOCTL_SET_PLL_FRAC_DATA       10
 33 - IOCTL_GET_PLL_FRAC_DATA       11                 60 - IOCTL_GET_PLL_FRAC_DATA       11
 34                                                    61 
 35 Refer EEMI API guide [0] for IOCTL specific pa     62 Refer EEMI API guide [0] for IOCTL specific parameters and other EEMI APIs.
 36                                                    63 
 37 References                                         64 References
 38 ----------                                         65 ----------
 39 [0] Embedded Energy Management Interface (EEMI     66 [0] Embedded Energy Management Interface (EEMI) API guide:
 40     https://www.xilinx.com/support/documentati     67     https://www.xilinx.com/support/documentation/user_guides/ug1200-eemi-api.pdf
                                                      

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php