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:   Thu, 23 Sep 2021 10:14:28 +0200
From:   Marek Szyprowski <>
To:     Maxime Ripard <>
Cc:     Andrzej Hajda <>,
        Sam Ravnborg <>,
        Daniel Vetter <>,
        David Airlie <>,
        Jonas Karlman <>,
        Laurent Pinchart <>,
        Thierry Reding <>,
        Maarten Lankhorst <>,
        Thomas Zimmermann <>,
        Neil Armstrong <>,
        Robert Foss <>,
        Jernej Skrabec <>,
        Sean Paul <>,,
        Kyungmin Park <>,,
        Xinliang Liu <>,
        Seung-Woo Kim <>,
        Tian Tao <>,
        Inki Dae <>,,,
        Rob Clark <>,,
        John Stultz <>,
        Chen Feng <>,
        Xinwei Kong <>,
        Joonyoung Shim <>
Subject: Re: [PATCH v4 24/24] drm/exynos: dsi: Adjust probe order

Hi Maxime,

On 22.09.2021 10:53, Maxime Ripard wrote:
> On Fri, Sep 17, 2021 at 02:35:05PM +0200, Marek Szyprowski wrote:
>> On 13.09.2021 12:30, Andrzej Hajda wrote:
>>> W dniu 10.09.2021 o 12:12, Maxime Ripard pisze:
>>>> Without proper care and an agreement between how DSI hosts and devices
>>>> drivers register their MIPI-DSI entities and potential components, we can
>>>> end up in a situation where the drivers can never probe.
>>>> Most drivers were taking evasive maneuvers to try to workaround this,
>>>> but not all of them were following the same conventions, resulting in
>>>> various incompatibilities between DSI hosts and devices.
>>>> Now that we have a sequence agreed upon and documented, let's convert
>>>> exynos to it.
>>>> Signed-off-by: Maxime Ripard <>
>>> This patch should be dropped, as it will probably break the driver.
>>> Exynos is already compatible with the pattern
>>> register-bus-then-get-sink, but it adds/removes panel/bridge
>>> dynamically, so it creates drm_device without waiting for downstream sink.
>> Right, this patch breaks Exynos DSI driver operation. Without it, the
>> whole series works fine on all Exynos based test boards.
> Thanks for testing. Did you have any board using one of those bridges in
> your test sample?

Nope, the only bridges I've tested are tc358764 and exynos-mic. However, 
both are used in a bit special way. The rest of my test boards just have 
a dsi panel.

Best regards
Marek Szyprowski, PhD
Samsung R&D Institute Poland

Powered by blists - more mailing lists