Re: [PATCH] drm/msm/dpu: Disable boot loader configured data paths

2022-02-16 Thread Dmitry Baryshkov
On 15/02/2022 18:15, Bjorn Andersson wrote: On Tue 15 Feb 08:44 CST 2022, Dmitry Baryshkov wrote: On 15/02/2022 07:37, Bjorn Andersson wrote: It's typical for the bootloader to configure CTL_0 for the boot splash or EFIFB, but for non-DSI use cases the DPU driver tend to pick another CTL and t

Re: [PATCH] drm/msm/dpu: Disable boot loader configured data paths

2022-02-15 Thread Bjorn Andersson
On Tue 15 Feb 08:44 CST 2022, Dmitry Baryshkov wrote: > On 15/02/2022 07:37, Bjorn Andersson wrote: > > It's typical for the bootloader to configure CTL_0 for the boot splash > > or EFIFB, but for non-DSI use cases the DPU driver tend to pick another > > CTL and the system might end up with two co

Re: [PATCH] drm/msm/dpu: Disable boot loader configured data paths

2022-02-15 Thread Dmitry Baryshkov
On 15/02/2022 07:37, Bjorn Andersson wrote: It's typical for the bootloader to configure CTL_0 for the boot splash or EFIFB, but for non-DSI use cases the DPU driver tend to pick another CTL and the system might end up with two configured data paths producing data on the same INTF. In particular

[PATCH] drm/msm/dpu: Disable boot loader configured data paths

2022-02-14 Thread Bjorn Andersson
It's typical for the bootloader to configure CTL_0 for the boot splash or EFIFB, but for non-DSI use cases the DPU driver tend to pick another CTL and the system might end up with two configured data paths producing data on the same INTF. In particular as the IOMMU configuration isn't retained from