From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpout-02.galae.net (smtpout-02.galae.net [185.246.84.56]) (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 44BE4332623 for ; Fri, 24 Apr 2026 08:25:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.246.84.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777019149; cv=none; b=ThmrEuusE4bPGyEmBwsKv2fgz7TKBtLG0IvpZEEdYlSTUdo2tJOdaEm27MKDnxcyNm656M0a6EJBbzpy0gPLUECxJ8VVY4q/GVg6C6BLYVY/jd5OZWGQtTolQJMRA6FYUm8N+Q69MtIAL5ZIluUuImVgR4RltauGlsE+6LlGtd4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777019149; c=relaxed/simple; bh=5+BUx2qSA912qQYrUExSpogjXL6NTO1wukuwyeTYxEg=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:Cc:To:From: References:In-Reply-To; b=UzoDpUXJz72Hmw6JkJ0qAaRlw7Gj85YZHZZlRmhyWDpcm+EC/gtiulIKZ2nIMT3JZtVNqJnCaLt9R0+9dI1zaTPJ+aADWWOLX50sxXEpT7NfeQ3dqDdw6Z/r1gIDMM3TCvenulKHr9fJk1xBTfPPXqav6medZ5fvtik4g5LjlGE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=DwDc9Q5h; arc=none smtp.client-ip=185.246.84.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="DwDc9Q5h" Received: from smtpout-01.galae.net (smtpout-01.galae.net [212.83.139.233]) by smtpout-02.galae.net (Postfix) with ESMTPS id 566E51A33DD; Fri, 24 Apr 2026 08:25:44 +0000 (UTC) Received: from mail.galae.net (mail.galae.net [212.83.136.155]) by smtpout-01.galae.net (Postfix) with ESMTPS id 23C55604EB; Fri, 24 Apr 2026 08:25:44 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 0AE7A10720728; Fri, 24 Apr 2026 10:25:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=dkim; t=1777019143; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=5+BUx2qSA912qQYrUExSpogjXL6NTO1wukuwyeTYxEg=; b=DwDc9Q5hEqzM/vxv94h5vObNwrcBr5XkEjcPQ5JPIrSbkbVboj8JUgz6oVETrjJ3hW1U/x SNLhPho6dc+EX7nk3hmdjqig1a8MyNxCRfK3Ih+TQ0vhxwxDCBSs3nfKeHGCOLwteEslzy C4YyxnuMhk3jhsuA3I4Xnob+c4IgllgXxw3lAdsxPMlWpnVfRmMCc3sVYMYYDBi00A3fu6 Xmu6DuSUbmR/FRjX5VLJcaeud7CxfD5YFhdS7eyU9ERo2YaI1ZqpQdGaRnBdx+PDsobolz Q9Comrv9svQ+fCNUkZxKVAfDTG5u9OfwzGL7rYe0fLJb9QF0BLpBWTKr8DFNIQ== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Fri, 24 Apr 2026 10:25:35 +0200 Message-Id: Subject: Re: [PATCH v3 1/1] drm: bridge: ti-sn65dsi83: Fix DSI mode flags for stable LVDS output Cc: , , , , , , , , , , , , , To: , , , From: "Luca Ceresoli" X-Mailer: aerc 0.20.1 References: <20260412053811.662461-1-tessolveupstream@gmail.com> <20260412053811.662461-2-tessolveupstream@gmail.com> <7056b23b-ed81-4d79-b782-5cfcb0102ef7@gmail.com> <60a24977-b181-40e4-bcf6-38b65af293e2@gmail.com> In-Reply-To: <60a24977-b181-40e4-bcf6-38b65af293e2@gmail.com> X-Last-TLS-Session-Version: TLSv1.3 Hello, On Thu Apr 23, 2026 at 11:16 AM CEST, tessolveupstream wrote: >> 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 th= e > SN65DSI83/84/86 datasheets covering DSI video transmission specifications= . Thanks for keeping on! I'm also trying to get info from TI, I'm keeping you up to date if that will happen. >> https://www.ti.com/lit/ds/symlink/sn65dsi84.pdf?ts=3D1776924088430&ref_u= rl=3Dhttps%253A%252F%252Fwww.ti.com%252Fproduct%252FSN65DSI84 > > As per datasheet Section 7.4.7, the device operates in DSI video mode wit= h > fixed horizontal timing, where HBP, and HFP are explicitly defined and ex= pected > to be present as part of the video line structure. The timing description= in > this section assumes standard non=E2=80=91burst video transmission with a= ll horizontal > blanking intervals accounted for. > > The datasheet does not document support for DSI video burst mode, This sentence seems incorrect. Section 7.4.7 starts with this sentence: "The SN65DSI84 supports burst video mode and non-burst video mode ...". Even though asa matter of fact it looks like many users have issues that get solved by disabling 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 colla= psed > or suppressed horizontal blanking, as enabled by MIPI_DSI_MODE_VIDEO_BURS= T, > MIPI_DSI_MODE_VIDEO_NO_HFP, or MIPI_DSI_MODE_VIDEO_NO_HBP. This is correct. We can still try to get TI feedback, but it that won't happen in, say, a few weeks then I think we should apply this patch. Luca -- Luca Ceresoli, Bootlin Embedded Linux and Kernel engineering https://bootlin.com