From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bali.collaboradmins.com (bali.collaboradmins.com [148.251.105.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6B7F944A724 for ; Wed, 15 Jul 2026 13:25:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=148.251.105.195 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784121917; cv=none; b=Bf4sHZkvf9369H5HideIxJMVG2A77iF2fLrYab569z2Oyp/1XV8Aa2wRhRcETzKakjFZBy497JTyWhtsw7w7MU/2Di+it6YEtKnPBHuuePP6Hi3Y0QHyDQwMME9o2GtVAnBIea5KVMeW7gKSLzJ39gwh5LghFpvqfkdle60FlmY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784121917; c=relaxed/simple; bh=X4hQ+PvvpEFhGE9C06CCHumxc5qZ+hbNEyoPw6puCII=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=AOiYbYA8JxpRAyfd2J6UtAqHXJPe/0STqZ7rO3aWISOnE2jNKb3WXPNxOCu1uvJ0QX7pfv6jDtJZ7RTO48JBaF9zwxcI7B92IZ6kKQG8qEmEHneqMdcKi1yFsB/fs5r/NM/MzciPU7UbQvPgiMsz3GWALiDern2z6A+9S8f4cIs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=collabora.com; spf=pass smtp.mailfrom=collabora.com; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b=oXumkldP; arc=none smtp.client-ip=148.251.105.195 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=collabora.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=collabora.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=collabora.com header.i=@collabora.com header.b="oXumkldP" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1784121912; bh=X4hQ+PvvpEFhGE9C06CCHumxc5qZ+hbNEyoPw6puCII=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=oXumkldPtd+e+lBP2cMWTV4Ri8iZUa5BqPUvQpqEoi09jZd+Z+fozCyBlv3i7buBm 0YhLBlvIADf/Rrg+TW28ks9sCjqpTLKRqGN31jUR4NQePGOGEN6Ps1fClmBiAj/Jss uvuviNrBdHRhichf9JK4C6pt5+2ahBzZkygh4KwwDJvr8sAuufHL31c59v//drDXWb EF3oUnOuKmjuunj8uy80HKIIr6pW29XMOexWQmokxrSz2S4ZrVnD0BlAB25uWYXBgg iwU9O+kHn6z0LCtaJrwzRaDLeTLQQvNvL1SWcIrpGWSFNU+MCgunihXM8xrnQcMMfl wr+jKqU3LQ4pA== Received: from [100.64.1.21] (unknown [100.64.1.21]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519) (No client certificate requested) (Authenticated sender: kholk11) by bali.collaboradmins.com (Postfix) with ESMTPSA id 2D4BE17E0DE9; Wed, 15 Jul 2026 15:25:12 +0200 (CEST) Message-ID: <0f719c00-3cf5-4403-afbf-713b07255981@collabora.com> Date: Wed, 15 Jul 2026 15:25:11 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] drm/mediatek: mtk_dsi: enable hs clock during pre-enable To: Esben Haabendal , Gary Bisson Cc: Chun-Kuang Hu , Philipp Zabel , David Airlie , Simona Vetter , Matthias Brugger , dri-devel@lists.freedesktop.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Adam Thiede , Thorsten Leemhuis References: <20260120-mtkdsi-v1-1-b0f4094f3ac3@gmail.com> <8733xko1ms.fsf@geanix.com> From: AngeloGioacchino Del Regno Content-Language: en-US In-Reply-To: <8733xko1ms.fsf@geanix.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 7/15/26 14:53, Esben Haabendal wrote: > 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 That clarifies a lot of things. The patch on mtk_dsi shall be reverted then. Cheers, Angelo