From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f45.google.com (mail-pj1-f45.google.com [209.85.216.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AED353E3C70 for ; Thu, 23 Apr 2026 09:16:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.216.45 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776935800; cv=none; b=Jl7Knuk4wi8Jf0V8llW51DZ/xQcUYp1G1OaylOM7W40IzjdAuohB4q20AxmNxULdwWFm5u/X0vhfT05Efgx2krvT/myfnj1i//5/uBRNkWTCP9uqThRnT7LHzXQ5uNOMhHW0vLPp5gL84fEXiU2VSkKWhe9Aww7L1XnNV9o5czo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776935800; c=relaxed/simple; bh=JnPvDXeZ7yAhEHyk05J2p66C4H8HJtnm4Mz6APbePzE=; h=Message-ID:Date:MIME-Version:Subject:From:To:Cc:References: In-Reply-To:Content-Type; b=m8Ac/dAfCi6mzeKzWiyh96IHppz2y6fTbVXtI64+d6akblEVW2UCdomd6xPmnocL+ibnk6MrYAktM742oxg7cgwBKmGc1Hz0p7BmYwg8YLaCtbu4ExCaUS0V5dICF9T7MYwOBRrPfR4SEu92/StwVk87jcppPK3Hia2w7Ax8wus= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=d0Xp6KYl; arc=none smtp.client-ip=209.85.216.45 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="d0Xp6KYl" Received: by mail-pj1-f45.google.com with SMTP id 98e67ed59e1d1-35fbca04006so3308990a91.1 for ; Thu, 23 Apr 2026 02:16:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1776935797; x=1777540597; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:from:subject:user-agent:mime-version:date:message-id:from:to :cc:subject:date:message-id:reply-to; bh=tJeE1AR9RIjmAJgGIUNU2WJKTNIwQfK4aOUPZv27pow=; b=d0Xp6KYlwmZLmpyU8rJiUcCJA+CZTtcWdTa64hHzYkqS10LpOj4CBl7IFdKuCcvzhj OZAKVwIGlIelDJAx/0iRXzbCGXDBR3gxN8g2Q1jiWj9Hn7z6w+R5ngFPsJpDvfs+Pgy8 k5HMqk9QxYMZGaV6AttcuqQIEtCyjs/NJL2G4X2f8otg69ewLmlYayflJIvnJ+z8Qkm4 nt4JZM8obkCRoekgfvEilxWWIW+GbwcGYiKHV+lZwHUR27V3gR7aJI63rgR3BU9xP4il CLQl3tdeDbYqc7GKjfSnPtaN2OIceXCBz0uFplOLT3MvDr/4mgVx8Z9P8rHs9ocgnRyJ tY/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776935797; x=1777540597; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:from:subject:user-agent:mime-version:date:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=tJeE1AR9RIjmAJgGIUNU2WJKTNIwQfK4aOUPZv27pow=; b=P48XXuSW6a5nOVKJHTnnZLIRiiR/M730ywQeqDZrvySffG9praa1F7Sq1tgwXJVFE1 cRltdu9SerFqTNBSyohppmVZml3zKrKxqXqWjcuONC4fW9msGsDVGN8WGqC9VSUWpSsg mgbI1v9RanNdeclh/3Ftd/tV2xfP9ATVxhhq8mr0h4/PkoOFy4/W0PmPmjG7SZUw7hdV qHe/+W23bJFFk8Ep4njqwgeMdga4RaXgneus8SWKD9IjdVlSg6jR/puZ6OUZqj12HcDH RL26Mr5UWlL+GGwTg7is2VR1nlLQdp/IUTlILPxlHpOeaWN5SsGf6+xep1bwt+JXcXH6 /iDw== X-Forwarded-Encrypted: i=1; AFNElJ8fu3KGmOLl18+hBGe8l21sOM5Dqs1LrJVnkJxh/qsoOZUveN+J/+hzNAmpOJ7u8gWtFV9fN+dnLxrlyi4=@vger.kernel.org X-Gm-Message-State: AOJu0Yz2/6y9iJ5VWivIRvBTqbcX0nMiY+xFJdge5IbtDiSUOHD0Zs+2 JbvIbeWyQk6k+UQJQAPPoY1JIkRfVUrc092UnLRGh8YYPCqZLoNZCZGj X-Gm-Gg: AeBDievTRPQRUWjMKzVOXhdr5o2ozsKEQnudbFzkaW1WJvu7oQnj+9Vd33b3InKGpI7 Rj/TgLiMjhkHrM3WrOvt8jG5RMfeM72551M4+3jML5PdG36KLL1tSpjEOpBu51rYB2y2Hg5tQ1n NGI3aSutUlMS1JdRfWmZOdqSF+e00Gw/i1n1LktbLzg22cgmtzpHJe1aqZbMnojgzuWn9rvJUwY uxvabfjQdkYfWpfhAMTmFjPJ3ZQTEAA3y4ZHeSwCAN0uWQhiULaWNuDjToHT3WyNUilgdA4PehQ xvevkHWy0CuTCceqjuPrO82VfQG4cS64MdPK0B54ueZe7flKZa5+Ja3T4IKD1vFIAVM6r3mCTQ4 2c0w8BvG2ukgnTVg48ZH1SzgJZ8u+HNpWdI+4meg1xpMSTbEf6L/PxB3vc4Ec3TkrCXXEiafGBA QCKlL3rPHmOut0lMNXSO4g7C8iOx+QXjzmUZDT+DQH6peol7RK8zw9h4CqRg== X-Received: by 2002:a17:90b:4cc5:b0:35d:a3b4:2f0d with SMTP id 98e67ed59e1d1-361403ca654mr26577237a91.6.1776935796573; Thu, 23 Apr 2026 02:16:36 -0700 (PDT) Received: from [172.16.20.13] ([136.226.252.245]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2b5fab3ac1fsm200162235ad.70.2026.04.23.02.16.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 23 Apr 2026 02:16:34 -0700 (PDT) Message-ID: <60a24977-b181-40e4-bcf6-38b65af293e2@gmail.com> Date: Thu, 23 Apr 2026 14:46:26 +0530 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 v3 1/1] drm: bridge: ti-sn65dsi83: Fix DSI mode flags for stable LVDS output From: tessolveupstream@gmail.com To: Luca Ceresoli , andrzej.hajda@intel.com, neil.armstrong@linaro.org, rfoss@kernel.org Cc: Laurent.pinchart@ideasonboard.com, jonas@kwiboo.se, jernej.skrabec@gmail.com, maarten.lankhorst@linux.intel.com, mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch, marex@denx.de, valentin@compulab.co.il, philippe.schenker@toradex.com, alexander.stein@ew.tq-group.com, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org References: <20260412053811.662461-1-tessolveupstream@gmail.com> <20260412053811.662461-2-tessolveupstream@gmail.com> <7056b23b-ed81-4d79-b782-5cfcb0102ef7@gmail.com> Content-Language: en-US In-Reply-To: <7056b23b-ed81-4d79-b782-5cfcb0102ef7@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 21-04-2026 11:31, tessolveupstream@gmail.com wrote: > > > On 16-04-2026 14:40, tessolveupstream@gmail.com wrote: >> >> >> On 15-04-2026 12:43, Luca Ceresoli wrote: >>> Hello Sudarshan, >>> >>> On Sun Apr 12, 2026 at 7:38 AM CEST, Sudarshan Shetty wrote: >>>> The current DSI mode configuration enables VIDEO_BURST and disables >>>> horizontal front porch (HFP) and back porch (HBP) transmission using >>>> MIPI_DSI_MODE_VIDEO_NO_HFP and MIPI_DSI_MODE_VIDEO_NO_HBP. >>>> >>>> However, the SN65DSI83/84 bridge relies on receiving full horizontal >>>> timing information over DSI in order to correctly reconstruct the LVDS >>>> output timings. When HFP and HBP are not transmitted, the bridge cannot >>>> recreate the required timing parameters, resulting in unstable or >>>> missing display output on some panels. >>>> >>>> Additionally, while burst mode is supported by the hardware, its use >>>> depends on continuous clock behavior from the DSI host. In practice, >>>> burst mode may introduce instability depending on the host controller >>>> implementation, as the DSI link may transition to low-power state >>>> between bursts. >>>> >>>> In testing, removing burst mode and ensuring full horizontal timing >>>> transmission results in stable LVDS output across affected panels. >>>> >>>> Update the DSI mode flags to: >>>> - Drop MIPI_DSI_MODE_VIDEO_BURST >>>> - Drop MIPI_DSI_MODE_VIDEO_NO_HFP >>>> - Drop MIPI_DSI_MODE_VIDEO_NO_HBP >>>> >>>> This aligns with common system configurations where non-burst mode is >>>> preferred and full timing information is transmitted over DSI. >>>> >>>> Signed-off-by: Sudarshan Shetty >>> >>> Thanks for having gone into the details and provide a good explanation for >>> the removal of these three flags. >>> >>> It would be still great to have authoritative info from TI, possibly as an >>> update to the documentation. >>> >>> I managed to test on a board with i.MX93, a TI SN65DSI84 and a 1920x1080p60 >>> panel, and: >>> >>> - no image shown with the current mainline driver >>> - it works by removing only MIPI_DSI_MODE_VIDEO_BURST (my current setup) >>> - it works with this patch applied >>> >>> Tested-by: Luca Ceresoli # imx93 1920x1080p60 >>> >> >> Thanks for testing the patch and for the Tested-by tag. >> I’ll reach out to TI for clarification on the DSI mode flag behavior and >> any documentation updates, and will share any feedback I receive, though I >> cannot guarantee a response. > > I had reached out to TI for clarification and any related documentation > updates, but I have not received any response so far.Given this, it is > uncertain whether we will be able to obtain further details or official > confirmation from TI in the near term. > > I would appreciate your guidance on how you would prefer us to proceed > from here. I followed up with TI, and they pointed us to the relevant sections in the SN65DSI83/84/86 datasheets covering DSI video transmission specifications. https://www.ti.com/lit/ds/symlink/sn65dsi84.pdf?ts=1776924088430&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FSN65DSI84 As per datasheet Section 7.4.7, the device operates in DSI video mode with fixed horizontal timing, where HBP, and HFP are explicitly defined and expected to be present as part of the video line structure. The timing description in this section assumes standard non‑burst video transmission with all horizontal blanking intervals accounted for. The datasheet does not document support for DSI video burst mode, nor does it mention support for omitting horizontal front or back porch intervals. In particular, there is no indication that the device can operate with collapsed or suppressed horizontal blanking, as enabled by MIPI_DSI_MODE_VIDEO_BURST, MIPI_DSI_MODE_VIDEO_NO_HFP, or MIPI_DSI_MODE_VIDEO_NO_HBP. Enabling these modes results in a mismatch between the host‑generated DSI timing and the device’s expected fixed timing model described in the datasheet, which leads to incorrect display behavior. This is consistent with our observations: the display fails when these modes are enabled, and operates correctly when using standard non‑burst video mode with explicit HBP/HFP timing. Therefore, removing these flags aligns the driver configuration with the datasheet‑defined timing requirements rather than acting as a workaround. They also shared the following E2E FAQ for reference: https://e2e.ti.com/support/interface-group/interface/f/interface-forum/1382976/faq-sn65dsi8x-programming-tools?tisearch=e2e-sitesearch&keymatch=sn65dsi86 However, they did not provide any additional clarification beyond what is already documented and indicated that there are currently no plans to further support or update the Linux driver. Given this, it seems unlikely that we will receive more detailed or authoritative guidance from TI on the specific mode flag usage. Please let me know how you would prefer us to proceed from here. >>> Luca >>> >>> -- >>> Luca Ceresoli, Bootlin >>> Embedded Linux and Kernel engineering >>> https://bootlin.com >> >