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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 02 Aug 2020 10:17:31 +0200
From:   Frank Wunderlich <>
        Chun-Kuang Hu <>
CC:     Jitao Shi <>,
        Philipp Zabel <>,
        David Airlie <>,
        linux-kernel <>,
        DRI Development <>,
        "moderated list:ARM/Mediatek SoC support" 
        Daniel Vetter <>,
        Matthias Brugger <>,
        Linux ARM <>
Subject: Re: [PATCH v2 4/5] drm/mediatek: dpi/dsi: change the getting possible_crtc way

Am 2. August 2020 05:07:41 MESZ schrieb Chun-Kuang Hu <>:

>I would like more information of why do this patch. For example:
>For current mediatek dsi encoder, its possible crtc is fixed in crtc
>0, and mediatek dpi encoder's possible crtc is fixed in crtc 1. In
>some SoC the possible crtc is not fixed in this case, so call
>mtk_drm_find_possible_crtc_by_comp() to find out the correct possible
sounds good (and you have much more knowledge about drm subsystem than i). I will take this for next version
regards Frank

Powered by blists - more mailing lists