Date:   Tue, 7 Dec 2021 19:54:40 +0200
From:   Imre Deak <imre.deak@intel.com>
To:     Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc:     Bjorn Andersson <bjorn.andersson@linaro.org>,
        Hans de Goede <hdegoede@redhat.com>,
        Prashant Malani <pmalani@chromium.org>,
        Doug Anderson <dianders@chromium.org>,
        Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
        Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
        David Airlie <airlied@linux.ie>,
        Daniel Vetter <daniel@ffwll.ch>,
        linux-arm-msm <linux-arm-msm@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Abhinav Kumar <abhinavk@codeaurora.org>,
        Stephen Boyd <swboyd@chromium.org>,
        Kuogee Hsieh <khsieh@codeaurora.org>,
        dri-devel <dri-devel@lists.freedesktop.org>,
        Vara Reddy <varar@codeaurora.org>,
        freedreno <freedreno@lists.freedesktop.org>,
        Enric Balletbo i Serra <enric.balletbo@collabora.com>,
        Benson Leung <bleung@chromium.org>
Subject: Re: [RFC] drm/msm/dp: Allow attaching a drm_panel
Message-ID: <20211207175440.GB727629@ideak-desk.fi.intel.com>
References: <YVumL1lHLqtb/HKS@ripper>
 <CAD=FV=W9uKq00wXn4H1ax0u2D=R8Wn3J-Je43uxcPyDtk7AK7Q@mail.gmail.com>
 <YVyMwsvLl6XalJxB@ripper>
 <CAD=FV=WY+g38p7--QKZCaQnSqx7VvdwC36jH-VKnrEWoxK=XHQ@mail.gmail.com>
 <YV0KBWxVtKgOp2Cj@ripper>
 <CAD=FV=X5JFE3u9BtxxocaUrYNSpYXJN90UJ8HOvXZE6oYiVsDQ@mail.gmail.com>
 <CACeCKac4b_ej87cQD692TNwpsoFsmBwDcSeLy5fp+pvLX1si7g@mail.gmail.com>
 <YV7JNH9QvI4cBz5s@kuha.fi.intel.com>
 <Ya6PTGN4zaZ8RD9K@ripper>
 <Ya9S3cFo0rOUotqY@kuha.fi.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Ya9S3cFo0rOUotqY@kuha.fi.intel.com>
Precedence: bulk

On Tue, Dec 07, 2021 at 02:26:05PM +0200, Heikki Krogerus wrote:
> +Hans and Imre
> [...]
>
> Originally I wanted an API that we could use to pass all the details
> that we have in the USB Type-C drivers (that would be the
> configuration and status) to the GPU drivers, but Hans was against
> that because, if I remember correctly, the OOB hotplug event may need
> to be delivered to the GPU drivers in some cases even when the
> connector is not USB Type-C connector, and he wanted a common API.
> Hans, please correct me if I got it wrong.
> 
> I think that the GPU drivers need to handle USB Type-C connectors
> separately one way or the other, but maybe the notification from the
> connector can continue to be generic - not USB Type-C specific.
> 
> Imre proposed that the GPU drivers should be able to query the
> DisplayPort configuration and status from the USB Type-C drivers
> instead of the USB Type-C drivers just dumping the information
> together with the notification about some event (so connection,
> disconnection or attention) like I originally proposed. Imre, please
> correct me if I misunderstood you :-).

I think the link config may be useful on Intel systems as well where the
hotplug event is delivered by another mean, the Gfx driver getting an
actual HW interrupt. Also on systems where the hotplug event does get
delivered OOB, the Gfx driver may want to query the current state, for
instance during booting or system resuming, independently of a hotplug
event.

Based on the above imo it would make sense to decouple the hotplug event
notification and the link configuration querying interface, or at least
make the querying possible in addition to the notification.

> I'm fine with anything, but we do need improvement here as you guys
> can see.
> 
> thanks,
> 
> -- 
> heikki