* Puranjay Mohan <p-mohan@xxxxxx> [220418 12:35]: > From: Suman Anna <s-anna@xxxxxx> > +/** > + * pruss_cfg_ocp_master_ports() - configure PRUSS OCP master ports > + * @pruss: the pruss instance handle > + * @enable: set to true for enabling or false for disabling the OCP master ports > + * > + * This function programs the PRUSS_SYSCFG.STANDBY_INIT bit either to enable or > + * disable the OCP master ports (applicable only on SoCs using OCP interconnect > + * like the OMAP family). Clearing the bit achieves dual functionalities - one > + * is to deassert the MStandby signal to the device PRCM, and the other is to > + * enable OCP master ports to allow accesses outside of the PRU-ICSS. The > + * function has to wait for the PRCM to acknowledge through the monitoring of > + * the PRUSS_SYSCFG.SUB_MWAIT bit when enabling master ports. Setting the bit > + * disables the master access, and also signals the PRCM that the PRUSS is ready > + * for Standby. Looks OK to me, some comments regarding runtime PM though for future patching though. Eventually we may want to handle this in drivers/bus/ti-sysc.c so it gets toggled based on runtime PM. The PRUSS sysc register seems to be just a new variant of sysc_regbits_omap4_simple with the standby and status bits added. If using runtime PM for the PRUSS instance is not suitable for managing the standby and status bits, then some comments should be added describing why finer grained control is needed for these bits beyond runtime PM. As far as I'm concerned, these can be done in separate changes, no need to update this patch. Regards, Tony
