On 24/09/2021 13:19, Jeya R wrote:
This patch series adds secure domains support. All DSP domains other
than CDSP are set as secure by default and CDSP is set as secure domain
This is going to break the existing devices that work with this driver?
Alteast the non cdsp cases.
like msm8996, sdm845, sm8250 ....
if fastrpc DT node carries secure domains property. If any process is
getting initialized using non-secure device and the dsp channel is
secure, then the session gets rejected.
Could you elaborate on what exactly you meant by secure here?
Is this SE linux policy we are talking about ?
Why can't we deal with this directly on /dev/[adsp|cdsp]-fastrpc nodes,
why do we need this extra secured node?
--srini
Jeya R (4):
dt-bindings: devicetree documentation for secure domain
misc: fastrpc: Add secure device node support
misc: fastrpc: Set channel as secure
misc: fastrpc: reject non-secure node for secure domain
.../devicetree/bindings/misc/qcom,fastrpc.txt | 6 ++
drivers/misc/fastrpc.c | 64 +++++++++++++++++++++-
2 files changed, 68 insertions(+), 2 deletions(-)
