[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250307210517.5xjfc6wntcbj3s4k@precision>
Date: Fri, 7 Mar 2025 15:05:17 -0600
From: Nishanth Menon <nm@...com>
To: Basharath Hussain Khaja <basharath@...thit.com>
CC: <ssantosh@...nel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <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>,
<parvathi@...thit.com>, Kevin Hilman
<khilman@...libre.com>
Subject: Re: [PATCH v2 1/1] soc: ti: PRUSS OCP configuration
On 18:29-20250108, Basharath Hussain Khaja wrote:
> From: Roger Quadros <rogerq@...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 either
> to enable or disable the OCP master ports (applicable only on SoCs
> using OCP interconnect like the OMAP family).
>
> Signed-off-by: Roger Quadros <rogerq@...com>
> Signed-off-by: Andrew F. Davis <afd@...com>
> Signed-off-by: Parvathi Pudi <parvathi@...thit.com>
> Signed-off-by: Basharath Hussain Khaja <basharath@...thit.com>
On the verge of applying this patch, looking deeper, I noticed
drivers/bus/ti-sysc.c managing the sysc controls. infact, I wonder if
b2745d92bb015cc4454d4195c4ce6e2852db397e ("bus: ti-sysc: Add support
for PRUSS SYSC type") could be merged with this?
Could you say why drivers/bus/ti-sysc.c would'nt be the right solution?
Ccying Kevin if he has any ideas about this.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists