From mboxrd@z Thu Jan 1 00:00:00 1970 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 7657EC44508 for ; Wed, 15 Jul 2026 12:53:29 +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-Type:MIME-Version: Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=xEwViipQaJZVXM9xLdF3SH6nxkka6iIr7lgTdrGkvYI=; b=e+E2eAOHF3UtnF9HjtATv4vixj SawykxLXlImEeEgGN9AfAJCO+T/HbCpfYnbaYTyRmIPteHfStSfwAaTP2JR+blbmt95LTu1HaRqQL NdDKi8BtdhPN5PvQiXuTh1NrXNR0wRssFpXWnCyxLheDV9uPp1qqab722p7Ry7kMO9lYr4W2c4JSB V4GZCRTVlBgsYtWaf50rOEZK1IHV0D8z/F01yEwTADqaGFzp6CexbR6qVJGDraWbvr0Lqcc7K/7GF xeluwelL03QlCv3P759zX/6QMkaE9qYxS7obMfV3JEcoaKbGn9//9O709WopuuiyUfONvXYfOTL8Q xqLq7+mQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wjz7A-0000000EraI-1PgZ; Wed, 15 Jul 2026 12:53:28 +0000 Received: from mail-43172.protonmail.ch ([185.70.43.172]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wjz77-0000000ErYh-1pQ7; Wed, 15 Jul 2026 12:53:27 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=geanix.com; s=protonmail3; t=1784119998; x=1784379198; bh=xEwViipQaJZVXM9xLdF3SH6nxkka6iIr7lgTdrGkvYI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID:From:To: Cc:Date:Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=Oxj58E8W3hKQZu0gvkYqCUZNpfUbBQ78VVenN6g9RIw4JHwjrEft/SGwCNV63zM7a 2Q7xDkapC/pwRDIyAOJX+qhgp7mkaYQ1WRaknqg0zER/f8uics62usPnCFmLtM++hz chlq7llvfrhyONj4ef/FcqTEwPVbOJEW8CHgUmMXqrRzQU9CN4tVdvulv/1XxFgLSu fY64gkXv2/1oav9kvx/MgaFCP/rf2z7oobqsuuBKCEb5kUSI63K81kkyuM6Wggw/H6 /+5ORu5ZuFxMRgJD7ayok7sl81etN/EQmzfVHek4fpQ7OP3pU+uq+23iCpjeLRS4kv CMe7pHG2/1yQA== X-Pm-Submission-Id: 4h0bgw0Q0rz1DFTS From: Esben Haabendal To: Gary Bisson Cc: Chun-Kuang Hu , Philipp Zabel , David Airlie , Simona Vetter , Matthias Brugger , AngeloGioacchino Del Regno , dri-devel@lists.freedesktop.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] drm/mediatek: mtk_dsi: enable hs clock during pre-enable In-Reply-To: <20260120-mtkdsi-v1-1-b0f4094f3ac3@gmail.com> (Gary Bisson's message of "Tue, 20 Jan 2026 12:36:59 +0100") References: <20260120-mtkdsi-v1-1-b0f4094f3ac3@gmail.com> Date: Wed, 15 Jul 2026 14:53:15 +0200 Message-ID: <8733xko1ms.fsf@geanix.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260715_055325_625268_279264F0 X-CRM114-Status: GOOD ( 10.36 ) 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 Gary Bisson writes: > Some bridges, such as the TI SN65DSI83, require the HS clock to be > running in order to lock its PLL during its own pre-enable function. > > Without this change, the bridge gives the following error: > sn65dsi83 14-002c: failed to lock PLL, ret=-110 > sn65dsi83 14-002c: Unexpected link status 0x01 > sn65dsi83 14-002c: reset the pipe > > Move the necessary functions from enable to pre-enable. > > Signed-off-by: Gary Bisson Hi I have run into the same problem, but in combination with another pipeline. I am seeing same problem with an i.MX8 using the nwl-dsi bridge and the dcss driver. I have submitted a fix that adresses the problem in the ti-sn65dsi83 driver instead. With a bit of luck, it can replace the fix proposed in this thread. See https://lore.kernel.org/all/20260711-ti-sn65dsi83-fixes-v1-2-d85eb5342b98@geanix.com/ /Esben