[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250426115424.518cfe88@akair>
Date: Sat, 26 Apr 2025 11:54:24 +0200
From: Andreas Kemnade <andreas@...nade.info>
To: Parvathi Pudi <parvathi@...thit.com>
Cc: aaro.koskinen@....fi, khilman@...libre.com, rogerq@...nel.org,
tony@...mide.com, linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
nm@...com, pratheesh@...com, prajith@...com, vigneshr@...com,
danishanwar@...com, praneeth@...com, srk@...com, rogerq@...com, afd@...com,
krishna@...thit.com, pmohan@...thit.com, mohan@...thit.com,
basharath@...thit.com
Subject: Re: [PATCH v1 1/1] bus: ti-sysc: PRUSS OCP configuration
Am Mon, 7 Apr 2025 12:51:34 +0530
schrieb Parvathi Pudi <parvathi@...thit.com>:
> Updates OCP master port configuration to enable memory access outside
> of the PRU-ICSS subsystem.
>
> This set of changes configures PRUSS_SYSCFG.STANDBY_INIT bit to enable
> the OCP master ports during resume sequence and disables the OCP master
> ports during suspend sequence (applicable only on SoCs using OCP
> interconnect like the OMAP family).
>
> Signed-off-by: Parvathi Pudi <parvathi@...thit.com>
mirrors what is done on module disable, so it looks sane.
Reviewed-by: Andreas Kemnade <andreas@...nade.info>
Powered by blists - more mailing lists