[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DBVCTYZVRR8C.39D28DAAS36UX@linaro.org>
Date: Wed, 06 Aug 2025 13:47:33 +0100
From: "Alexey Klimov" <alexey.klimov@...aro.org>
To: "Bjorn Andersson" <andersson@...nel.org>
Cc: <konradybcio@...nel.org>, <linux-arm-msm@...r.kernel.org>,
<robh@...nel.org>, <krzk+dt@...nel.org>, <conor+dt@...nel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<srini@...nel.org>, <quic_ekangupt@...cinc.com>,
<krzysztof.kozlowski@...aro.org>, <dmitry.baryshkov@....qualcomm.com>
Subject: Re: [PATCH v2] arm64: dts: qcom: sm8750: Add adsp fastrpc
nodes/support
On Wed Aug 6, 2025 at 1:25 AM BST, Bjorn Andersson wrote:
Previous version was sent few months back.
> On Tue, Aug 05, 2025 at 05:20:41PM +0100, Alexey Klimov wrote:
>> While at this, also add required memory region for adsp fastrpc.
>
> Please https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
> rather than lazily continue the subject.
Ok.
It also seems that some other commits that were merged doesn't
really describe addition of fastrpc nodes well.
> Also, the way you wrote this makes me believe adsp_rpc_remote_heap_mem
> is optional, and as I don't know what it's for I don't understand why
> that would be part of this patch.
Yeah, after looking further at the bindings I agree that this should be
described better.
Although some of this is confusing:
>required memory region
>adsp_rpc_remote_heap_mem is optional
Anyhow this mem region seems to be optional so I'll try to split it into
two patches (need to check that dtbs check will be happy with that).
It also seems that when adsp_rpc_remote_heap_mem was merged for other
dtsi-es then no questions were asked.
>> Tested on sm8750-mtp device with adsprpdcd.
>
> Just adsprpdcd?
Yeah, I forgot to mention that getserial can libcalculator tests.
> Is that sufficient to say that fastrpc is functional? Or
> at least that the information here is sufficiently tested?
The testing of fastrpc for adsp is quite limited. If you or Qualcomm can
provide the usable tests to run and verify then please do so.
I think what happens is that often the info for fastrpc nodes just being
copied and filled in with info from downstream with no requests to provide
test results.
Here it was tested with adsprpdcd with compressed playback and two tests
above I forgot to mention.
[..]
Thanks,
Alexey
Powered by blists - more mailing lists