[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cy3bb2vch7pg24ldjhcq3pg456n5vrdwqsdcwzpghytrxzo6ta@hhhr3nelfipy>
Date: Mon, 10 Jun 2024 21:24:53 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Ekansh Gupta <quic_ekangupt@...cinc.com>
Cc: srinivas.kandagatla@...aro.org, linux-arm-msm@...r.kernel.org,
gregkh@...uxfoundation.org, quic_bkumar@...cinc.com, linux-kernel@...r.kernel.org,
quic_chennak@...cinc.com
Subject: Re: [PATCH v4 05/11] misc: fastrpc: Add static PD restart support
On Mon, Jun 10, 2024 at 02:35:48PM +0530, Ekansh Gupta wrote:
>
>
> On 6/7/2024 4:55 PM, Dmitry Baryshkov wrote:
> > On Thu, Jun 06, 2024 at 10:29:25PM +0530, Ekansh Gupta wrote:
> >> Static PDs are created on DSPs to support specific use cases like Audio
> >> and Sensors. The static PDs uses any CPU requirements like file
> >> operations or memory need with the help of a daemon running on the CPU.
> > What do you mean by 'CPU requirements' here?
> Something like file system request or any memory requirement. For these types of requirements
> PD will rely on CPU process.
So, this is not 'CPU requirements'. It should be something like
'requests to the HLOS'. CPU requirements would usually mean something
requiring CPU cycles or min/max freq, etc.
>
> Planning to drop this patch from the series and move the pd notification specific implementations
> to a different .c file as per Caleb's suggestion.
>
> I'll address all other comments in the new patch series.
Ack
--
With best wishes
Dmitry
Powered by blists - more mailing lists