[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YbcnEp5+4y5qXC60@gerhold.net>
Date: Mon, 13 Dec 2021 11:57:22 +0100
From: Stephan Gerhold <stephan@...hold.net>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: robh+dt@...nel.org, gregkh@...uxfoundation.org,
devicetree@...r.kernel.org, ekangupt@....qualcomm.com,
jeyr@...eaurora.org, bkumar@....qualcomm.com,
linux-kernel@...r.kernel.org, bjorn.andersson@...aro.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v2 5/8] dt-bindings: misc: add property to support
non-secure DSP
On Thu, Dec 09, 2021 at 12:06:23PM +0000, Srinivas Kandagatla wrote:
> From: Jeya R <jeyr@...eaurora.org>
>
> Add property to set DSP domain as non-secure.
>
> ADSP/MDSP/SDSP are by default secured, where as CDSP can be either be
> secured/unsecured.
Wouldn't it be easier to avoid the negation and add a "qcom,secure-domain"
property instead? Given PATCH 8/8 ("arm64: dts: qcom: add non-secure
domain property to fastrpc nodes") it looks like you are intentionally
breaking DT compatibility here, but this patch does not justify why this
is necessary.
Thanks,
Stephan
Powered by blists - more mailing lists