mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-21 03:33:59 +08:00
8ba85306ba
The scalers of overlays and writeback do not have any constraints on downscale ratio when operating in memory to memory mode. This is because in memory to memory mode, we aren't connected to a display which needs data output at the rate of pixel clock. The scalers can perform as much downscaling as needed, the rate at which the scaler outputs is adjusted accordingly. Relax constraints related to downscaling based on whether the input overlays are connected to writeback in memory to memory mode. We pass a mem_to_mem boolean parameter to dispc_ovl_setup() from APPLY. This is currently set to false, this will later be configured to the correct value based on whether the overlay is connected to writeback or not. Do the same later for writeback when writeback is configured. In the scaling calculation code, we calculate the minimum amount of core clock we need to achieve the required downscaling. If we are in memory to memory mode, we set this to a very small value(1 in this case), this value would always be lesser than the actual DISPC core clock value, and hence the scaling checks would succeed. We take care that pixel clock isn't calculated for writeback and the overlays connected to it when in memory to memory mode. A pixel clock in such cases doesn't make sense. Signed-off-by: Archit Taneja <archit@ti.com> |
||
|---|---|---|
| .. | ||
| apply.c | ||
| core.c | ||
| dispc_coefs.c | ||
| dispc.c | ||
| dispc.h | ||
| display.c | ||
| dpi.c | ||
| dsi.c | ||
| dss_features.c | ||
| dss_features.h | ||
| dss.c | ||
| dss.h | ||
| hdmi_panel.c | ||
| hdmi.c | ||
| Kconfig | ||
| Makefile | ||
| manager-sysfs.c | ||
| manager.c | ||
| output.c | ||
| overlay-sysfs.c | ||
| overlay.c | ||
| rfbi.c | ||
| sdi.c | ||
| ti_hdmi_4xxx_ip.c | ||
| ti_hdmi_4xxx_ip.h | ||
| ti_hdmi.h | ||
| venc_panel.c | ||
| venc.c | ||