Messages in this thread | | | From | Frank Wunderlich <> | Subject | Aw: Re: Re: Re: [PATCH v2 1/5] drm/mediatek: config component output by device node port | Date | Tue, 4 Aug 2020 11:53:28 +0200 |
| |
Hi,
i've printed the mtk_comp_id after the modification-loops...
[ 5.480848] main: [ 5.480851] DDP_COMPONENT_OVL0 [ 5.482776] DDP_COMPONENT_RDMA0 [ 5.485827] DDP_COMPONENT_COLOR0 [ 5.488978] DDP_COMPONENT_BLS [ 5.492206] DDP_COMPONENT_DPI0 [ 5.495170] ext: [ 5.498233] DDP_COMPONENT_RDMA1 [ 5.500068] DDP_COMPONENT_DPI0
so only the main-path was replaced with DPI at the end. so currently the DSI is not connected (or i move it to ext). have now added new structs for mt7623 with swapped DPI0/DSI0 and commented out the code from Patch 1...compatible was already mt7623 with 2701 as fallback, so no dts-change needed...
now i need to look which changes in dts can be dropped...at least the bls=>dpi, right?
regards Frank
> Gesendet: Montag, 03. August 2020 um 18:27 Uhr > Von: "Chun-Kuang Hu" <chunkuang.hu@kernel.org>
> Yes, this is what I mean, but I think it need not output to pmw. > But now I have a solution that you need not to modify binding document. > Because now mt7623 has a different routing than mt2701, and this > patch's approach is to use different port setting in each device tree. > My solution is that these two SoC has different compatible string: > "mediatek,mt7623-mmsys" and "mediatek,mt2701-mmsys". For now, > "mediatek,mt2701-mmsys" has its data as > > static const struct mtk_mmsys_driver_data mt2701_mmsys_driver_data = { > .main_path = mt2701_mtk_ddp_main, > .main_len = ARRAY_SIZE(mt2701_mtk_ddp_main), > .ext_path = mt2701_mtk_ddp_ext, > .ext_len = ARRAY_SIZE(mt2701_mtk_ddp_ext), > .shadow_register = true, > }; > > I think you could create a data for "mediatek,mt7623-mmsys" which has > a different routing.
| |