lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 03 Aug 2020 20:02:38 +0200 From: Frank Wunderlich <frank-w@...lic-files.de> To: linux-mediatek@...ts.infradead.org, Chun-Kuang Hu <chunkuang.hu@...nel.org>, ryder.lee@...iatek.com CC: Daniel Vetter <daniel@...ll.ch>, David Airlie <airlied@...ux.ie>, linux-kernel <linux-kernel@...r.kernel.org>, DRI Development <dri-devel@...ts.freedesktop.org>, "moderated list:ARM/Mediatek SoC support" <linux-mediatek@...ts.infradead.org>, Philipp Zabel <p.zabel@...gutronix.de>, Matthias Brugger <matthias.bgg@...il.com>, Bibby Hsieh <bibby.hsieh@...iatek.com>, Linux ARM <linux-arm-kernel@...ts.infradead.org> Subject: Re: Re: Re: [PATCH v2 1/5] drm/mediatek: config component output by device node port Am 3. August 2020 18:27:02 MESZ schrieb Chun-Kuang Hu <chunkuang.hu@...nel.org>: >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. The paths are defined as this: static enum mtk_ddp_comp_id mt2701_mtk_ddp_main[] = { DDP_COMPONENT_OVL0, DDP_COMPONENT_RDMA0, DDP_COMPONENT_COLOR0, DDP_COMPONENT_BLS, DDP_COMPONENT_DSI0,}; static enum mtk_ddp_comp_id mt2701_mtk_ddp_ext[] = { DDP_COMPONENT_RDMA1, DDP_COMPONENT_DPI0,}; First thing i notice is that main=dsi and ext=dpi (hdmi). I guess dpi should be main,right? And bls is actually routed to dpi...how about the other components? The 2 loops are not really clear to me (except 1st overwrites mt2701 main-path and second ext_path based on ports/endpoints) but this only applies from bls-dpi-hdmi-connector,not xdma/color or similar. Or should be main-path (or external) only bls and dpi? It looks like it only swappes dpi and dsi in my case. @Ryder Lee can you explain it? regards Frank
Powered by blists - more mailing lists