From patchwork Thu Mar 30 14:20:27 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: AngeloGioacchino Del Regno X-Patchwork-Id: 13194246 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A6BE5C6FD1D for ; Thu, 30 Mar 2023 14:20:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: MIME-Version:Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-Type: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Owner; bh=0M4Ry3df6NVrXO0G3WC4aU/wNHteRp+/VH+Gpm1PEfQ=; b=hT+vkg5QUtB5LGfafzNs6akdut uzQDf1thoZZjCTkm21spm/83KdZuTJeJF8XU0hre/iteStG7Kw9QNMFNCU8KgSVbaeiakYQwgqNR6 xYpB43Mq4jzRRwjz+11/iDDxCTPNxovBykVGWm6f67kqen7Wg2WkHx8/ZbKO9AjSNkO1a5Uju0RKN OVUuLmboKzPyGyikJHGxYG+FXqkZJSrrsAN6Sw4XmK0uiDDNMmPhdv2CrZcO/EUjTKF2o6AumYR/E ltXCDocNixueFNKKNcaR/DusnDS0nlPpXN5lPNhTjTM2Pwek6XvHIVgYxzPW+DmPxgXNAVHDtr4ti Phj2xSIA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1pht8x-0042J5-2j; Thu, 30 Mar 2023 14:20:47 +0000 Received: from madras.collabora.co.uk ([46.235.227.172]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1pht8s-0042Da-06; Thu, 30 Mar 2023 14:20:43 +0000 Received: from IcarusMOD.eternityproject.eu (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id A0F6B66030CD; Thu, 30 Mar 2023 15:20:39 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1680186040; bh=z67vNzKi9aaIqAtcwOlUEH/djDA/nzpldmj/FIyFeFE=; h=From:To:Cc:Subject:Date:From; b=SmUL/fcPVWMP9xKCbKnTdqhI6xu8GRuh0Zi1NBwpLtsx9mTCG8Ul+uSFZ5bAV6Okm V8FNs7jaUTWYRylJVu3sHHPC58NTPNmVPRhsFRq2UQHFq+1hIOrj/4SLTRkGwQejyF fHqB5FJy8V2zJNjxibyFvbI1I9SRkigAJzpaUMjyHIk/KajqkhkjLORwwOVQnxJKtY ivDZlTVRsAXuSGTI3F7Bokq4NxiGPX9PatVYPpYKxLY709DwmM3DfRikyIapP9HZTs eJ3Dg1Xs/wNoI8qarNNTy8TFePa8xIbdLbvjmASgRJBcx7jezG2FAH8bq5TCkKCND4 qXHkXzHzFGzAw== From: AngeloGioacchino Del Regno To: chunkuang.hu@kernel.org Cc: p.zabel@pengutronix.de, airlied@gmail.com, daniel@ffwll.ch, matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com, dri-devel@lists.freedesktop.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel@collabora.com, wenst@chromium.org Subject: [PATCH v2 0/8] MediaTek DisplayPort: support eDP and aux-bus Date: Thu, 30 Mar 2023 16:20:27 +0200 Message-Id: <20230330142035.191399-1-angelogioacchino.delregno@collabora.com> X-Mailer: git-send-email 2.40.0 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230330_072042_197663_0F3E56C0 X-CRM114-Status: GOOD ( 18.24 ) X-BeenThere: linux-mediatek@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-mediatek" Errors-To: linux-mediatek-bounces+linux-mediatek=archiver.kernel.org@lists.infradead.org Changes in v2: - Sorry, the v1 send got broken as I forgot to remove old patches in my send folder. This series adds "real" support for eDP in the mtk-dp DisplayPort driver. Explaining the "real": Before this change, the DisplayPort driver did support eDP to some extent, but it was treating it entirely like a regular DP interface which is partially fine, after all, embedded DisplayPort *is* actually DisplayPort, but there might be some differences to account for... and this is for both small performance improvements and, more importantly, for correct functionality in some systems. Functionality first: One of the common differences found in various boards implementing eDP and machines using an eDP panel is that many times the HPD line is not connected. This *must* be accounted for: at startup, this specific IP will raise a HPD interrupt (which should maybe be ignored... as it does not appear to be a "real" event...) that will make the eDP panel to be detected and to actually work but, after a suspend-resume cycle, there will be no HPD interrupt (as there's no HPD line in my case!) producing a functionality issue - specifically, the DP Link Training fails because the panel doesn't get powered up, then it stays black and won't work until rebooting the machine (or removing and reinserting the module I think, but I haven't tried that). Now for.. both: eDP panels are *e*DP because they are *not* removable (in the sense that you can't unplug the cable without disassembling the machine, in which case, the machine shall be powered down..!): this (correct) assumption makes us able to solve some issues and to also gain a little performance during PM operations. What was done here is: - Caching the EDID if the panel is eDP: we're always going to read the same data everytime, so we can just cache that (as it's small enough) shortening PM resume times for the eDP driver instance; - Always return connector_status_connected if it's eDP: non-removable means connector_status_disconnected can't happen during runtime... this also saves us some time and even power, as we won't have to perform yet another power cycle of the HW; - Added aux-bus support! This makes us able to rely on panel autodetection from the EDID, avoiding to add more and more panel timings to panel-edp and, even better, allowing to use one panel node in devicetrees for multiple variants of the same machine since, at that point, it's not important to "preventively know" what panel we have (eh, it's autodetected...!). This was tested on a MT8195 Cherry Tomato Chromebook (panel-edp on aux-bus) P.S.: For your own testing commodity, here's a reference devicetree: &edp_tx { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&edptx_pins_default>; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; edp_in: endpoint { remote-endpoint = <&dp_intf0_out>; }; }; port@1 { reg = <1>; edp_out: endpoint { data-lanes = <0 1 2 3>; remote-endpoint = <&panel_in>; }; }; }; aux-bus { panel: panel { compatible = "edp-panel"; power-supply = <&pp3300_disp_x>; backlight = <&backlight_lcd0>; port { panel_in: endpoint { remote-endpoint = <&edp_out>; }; }; }; }; }; AngeloGioacchino Del Regno (8): drm/mediatek: dp: Cache EDID for eDP panel drm/mediatek: dp: Move AUX and panel poweron/off sequence to function drm/mediatek: dp: Always return connected status for eDP in .detect() drm/mediatek: dp: Always set cable_plugged_in at resume for eDP panel drm/mediatek: dp: Change logging to dev for mtk_dp_aux_transfer() drm/mediatek: dp: Enable event interrupt only when bridge attached drm/mediatek: dp: Use devm variant of drm_bridge_add() drm/mediatek: dp: Add support for embedded DisplayPort aux-bus drivers/gpu/drm/mediatek/mtk_dp.c | 172 ++++++++++++++++++------------ 1 file changed, 106 insertions(+), 66 deletions(-)