linux-kernel - Re: [PATCH v1 0/2] Revert chrontel-ch7033 byteswap order series

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 12 Sep 2022 16:35:47 -0500
From:   Chris Morgan <macroalpha82@...il.com>
To:     Robert Foss <robert.foss@...aro.org>
Cc:     andrzej.hajda@...el.com, narmstrong@...libre.com,
        Laurent.pinchart@...asonboard.com, jonas@...boo.se,
        jernej.skrabec@...il.com, airlied@...ux.ie, daniel@...ll.ch,
        robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        dianders@...omium.org, lkundrak@...sk,
        dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Chris Morgan <macromorgan@...mail.com>, tzimmermann@...e.de,
        javierm@...hat.com, maarten.lankhorst@...ux.intel.com,
        mripard@...nel.org
Subject: Re: [PATCH v1 0/2] Revert chrontel-ch7033 byteswap order series

On Mon, Sep 12, 2022 at 01:38:54PM +0200, Robert Foss wrote:
> After applying the "chrontel-ch7033: Add byteswap order option" series,
> Laurent reported an issues with the approach. Since no fix has been submitted
> for the issues outlined in time for the next kernel release, I'd like to
> revert this series for now.
> 
> Just to be clear I would very much like to see a v3 of this[1] series, where the
> issues outlined have been fixed.

I will work on a v3 soon, I just have to finish a few other things first.

That said, I'm not very familiar with what we're trying to do in an automated
fashion. In my use case I have DPI output (from an Allwinner R8 to this bridge)
which then connects via HDMI. I'm aware that we should be able to get the color
space information from the HDMI connector, correct? Is it that information I
would then need to use to set the bridge colorspace, or is it the color info
from the DPI connector I'm using?

I'm still pretty new to DRM drivers so this is mostly new to me. Thank you.

> 
> [1] https://lore.kernel.org/all/20220902153906.31000-1-macroalpha82@gmail.com/
> 
> Robert Foss (2):
>   Revert "dt-bindings: Add byteswap order to chrontel ch7033"
>   Revert "drm/bridge: ti-sn65dsi86: Implement bridge connector
>     operations for DP"
> 
>  .../display/bridge/chrontel,ch7033.yaml       | 13 ---------
>  drivers/gpu/drm/bridge/ti-sn65dsi86.c         | 28 -------------------
>  2 files changed, 41 deletions(-)
> 
> -- 
> 2.34.1
>