On 26/07/2022 14:01, Sibi Sankar wrote: >>>> I think you may be right; I just applied this patchset to -next >>>> (20220722) and i do not see the error message there. On my 5.19-rc7 >>>> tree, i am also testing a patchset that enables qcom devices to access >>>> efivars, so possibly we are ending up in secure world there? >>> >>> Actually mapping of IO space should not touch secure world, so this was >>> a long shot assuming you test it on the next. >>> >> >> The memory region specified in device tree overlaps with the llcc system >> cache controller node. Steev probably had the QCOM_LLCC config enabled >> when he tested it out on his branch. > > From what I see we can probably get away with restricting the llcc_base > reg region to just llcc0_common region and leave the lcc-bwmon as is. Och, that IO mapping for llcc is quite big. I'll try that. Best regards, Krzysztof
