Commit 38c0b252 authored by Ronak Jain's avatar Ronak Jain
Browse files

feat(plat/xilinx/zynqmp): sync IOCTL IDs



Sync IOCTL IDs in order to avoid conflict with other components like,
 Linux and firmware. Hence assigning value to IDs to make it more
 specific.
Signed-off-by: default avatarRonak Jain <ronak.jain@xilinx.com>
Change-Id: I11ae679fbd0a953290306b62d661cc142f50dc28
parent be3a51ce
...@@ -15,28 +15,40 @@ ...@@ -15,28 +15,40 @@
//ioctl id //ioctl id
enum { enum {
IOCTL_GET_RPU_OPER_MODE, IOCTL_GET_RPU_OPER_MODE = 0,
IOCTL_SET_RPU_OPER_MODE, IOCTL_SET_RPU_OPER_MODE = 1,
IOCTL_RPU_BOOT_ADDR_CONFIG, IOCTL_RPU_BOOT_ADDR_CONFIG = 2,
IOCTL_TCM_COMB_CONFIG, IOCTL_TCM_COMB_CONFIG = 3,
IOCTL_SET_TAPDELAY_BYPASS, IOCTL_SET_TAPDELAY_BYPASS = 4,
IOCTL_SET_SGMII_MODE, IOCTL_SET_SGMII_MODE = 5,
IOCTL_SD_DLL_RESET, IOCTL_SD_DLL_RESET = 6,
IOCTL_SET_SD_TAPDELAY, IOCTL_SET_SD_TAPDELAY = 7,
/* Ioctl for clock driver */ /* Ioctl for clock driver */
IOCTL_SET_PLL_FRAC_MODE, IOCTL_SET_PLL_FRAC_MODE = 8,
IOCTL_GET_PLL_FRAC_MODE, IOCTL_GET_PLL_FRAC_MODE = 9,
IOCTL_SET_PLL_FRAC_DATA, IOCTL_SET_PLL_FRAC_DATA = 10,
IOCTL_GET_PLL_FRAC_DATA, IOCTL_GET_PLL_FRAC_DATA = 11,
IOCTL_WRITE_GGS, IOCTL_WRITE_GGS = 12,
IOCTL_READ_GGS, IOCTL_READ_GGS = 13,
IOCTL_WRITE_PGGS, IOCTL_WRITE_PGGS = 14,
IOCTL_READ_PGGS, IOCTL_READ_PGGS = 15,
/* IOCTL for ULPI reset */ /* IOCTL for ULPI reset */
IOCTL_ULPI_RESET, IOCTL_ULPI_RESET = 16,
/* Set healthy bit value */ /* Set healthy bit value */
IOCTL_SET_BOOT_HEALTH_STATUS, IOCTL_SET_BOOT_HEALTH_STATUS = 17,
IOCTL_AFI, IOCTL_AFI = 18,
/* Probe counter read/write */
IOCTL_PROBE_COUNTER_READ = 19,
IOCTL_PROBE_COUNTER_WRITE = 20,
IOCTL_OSPI_MUX_SELECT = 21,
/* IOCTL for USB power request */
IOCTL_USB_SET_STATE = 22,
/* IOCTL to get last reset reason */
IOCTL_GET_LAST_RESET_REASON = 23,
/* AI engine NPI ISR clear */
IOCTL_AIE_ISR_CLEAR = 24,
/* Register SGI to ATF */
IOCTL_REGISTER_SGI = 25,
}; };
//RPU operation mode //RPU operation mode
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment