12:43 <DavidHeidelberg[m]> bamse: Hello, do you recall from commit `ARM: dts: qcom: apq8064: Add syscon for sic-non-secure` (2016), what sic non-secure means? I didn't found it anywhere outside APQ8064

12:43 <DavidHeidelberg[m]> nor on internet

13:18 <DavidHeidelberg[m]> sboyd: Hey! Question regarding to `clk: qcom: Add KPSS ACC/GCC driver`, does this [ https://github.com/apq8064-mainline/linux/blob/qcom-apq8064-next/arch/arm/boot/dts/qcom-ipq8064.dtsi#L781 ] node look correct? in case it does, should make sense use same compatible here: https://github.com/apq8064-mainline/linux/blob/qcom-apq8064-next/arch/arm/boot/dts/qcom-apq8064.dtsi#L865 ?

13:19 <DavidHeidelberg[m]> it seems little bit unusual, since docs doesn't mention syscon, on other hand it makes sense to me as it is used

16:33 <bamse> DavidHeidelberg[m]: recall...no...but i found a patch that references it

16:33 <bamse> DavidHeidelberg[m]: it seems to be used for invoking interrupts on the sensor processor

16:36 <bamse> ahh yeah that patch made it upstream as well, nice

16:37 <DavidHeidelberg[m]> bamse: so let say I can put `compatible = "qcom,sic-non-secure", "syscon";` and referencing `qcom,sic-non-secure` from `syscon.yaml`?

16:38 <bamse> DavidHeidelberg[m]: so in qcom-apq8064.dtsi we have &l2cc and &sps_sic_non_secure as syscons and smd and smsm just points to those...

16:38 <DavidHeidelberg[m]> yes

16:38 <bamse> this predates ab460a2e72da ("rpmsg: qcom_smd: Access APCS through mailbox framework")

16:38 <bamse> which was when we switched to properly describe that

16:38 <bamse> yeah, i think your suggestion makes sense