From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lelv0142.ext.ti.com (lelv0142.ext.ti.com [198.47.23.249]) (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 C7DD1155336 for ; Sat, 22 Jun 2024 11:47:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.23.249 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719056853; cv=none; b=i3sXaFUog8H5xKB52CX7IlhBckySmWkv80gwQbQAOpEAawd280VVgO1gcKAPXaQfSj/GMdPe6VKTWOZusmy9xrt9WyFexJ2FAaduU07gLL1aihrV1KPrMaKeU2RCe4eLxBX/4dhMH63nhMIuwjvvdxrlv1Kgr+dPV7byOxmKO7M= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1719056853; c=relaxed/simple; bh=sCk3YO9WOQvhuZMzjKpAZkJycJUs/0rLbD46yhu7gyg=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=k64Z8V5gdHJtBEt5HbhRqiO/8ieIRldhvcNLyvWEVXkDz6SYevLDd5OxzcdIn6JJKhVTUuHfVUKWKFDyfiKpkpbXaVSsbhkyBQta/3nNe7TxEY8hK1OuFL350JYVgvYcYf6FGqAon/FO1GazlpYUqDAgTkIHgknGOiVb1o/hn70= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com; spf=pass smtp.mailfrom=ti.com; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b=H3KsNqXw; arc=none smtp.client-ip=198.47.23.249 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="H3KsNqXw" Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0142.ext.ti.com (8.15.2/8.15.2) with ESMTP id 45MBl6HV016063; Sat, 22 Jun 2024 06:47:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1719056827; bh=j4OrdUKtJX/7en/BuYO+MHA6aUkbfOxmzOwAqmp5pT0=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=H3KsNqXwO/dLY/aCjOEILTrM0Z4Yx715Up3ToB4teSZlmlHI9pgV/kjUWN/UAg/rV Ed9o0riOJJGdILb9WxxTSTyDPSd7QP9oTdtxB5FO8StSFLf83kaK6CneNYkJ0A7HAv iANUXqMxQFBy0MOb2SD7+2kEhGJQY7iKmFsDk0JQ= Received: from DFLE100.ent.ti.com (dfle100.ent.ti.com [10.64.6.21]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 45MBl6Ki028337 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 22 Jun 2024 06:47:06 -0500 Received: from DFLE112.ent.ti.com (10.64.6.33) by DFLE100.ent.ti.com (10.64.6.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Sat, 22 Jun 2024 06:47:06 -0500 Received: from lelvsmtp6.itg.ti.com (10.180.75.249) by DFLE112.ent.ti.com (10.64.6.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Sat, 22 Jun 2024 06:47:06 -0500 Received: from [10.249.129.248] ([10.249.129.248]) by lelvsmtp6.itg.ti.com (8.15.2/8.15.2) with ESMTP id 45MBkxte067399; Sat, 22 Jun 2024 06:47:00 -0500 Message-ID: <71e809fa-b471-4bb3-8f7d-e497397c0de4@ti.com> Date: Sat, 22 Jun 2024 17:16:58 +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 v2 0/2] drm/bridge: tc358767: Fix DRM_BRIDGE_ATTACH_NO_CONNECTOR case Content-Language: en-US To: Alexander Stein , Dmitry Baryshkov , Jan Kiszka , Marek Vasut , Tomi Valkeinen CC: Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Daniel Vetter , Sam Ravnborg , , References: <20231108-tc358767-v2-0-25c5f70a2159@ideasonboard.com> <2f3bb86b-6f8c-4807-985e-344a0c47864c@siemens.com> <3277848.aeNJFYEL58@steina-w> <36ef53b6-57a3-42e4-95ef-a10eef4ca1c9@siemens.com> From: Aradhya Bhatia In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 On 17-Jun-24 13:41, Dmitry Baryshkov wrote: > On Mon, Jun 17, 2024 at 07:40:32AM GMT, Jan Kiszka wrote: >> On 16.02.24 15:57, Marek Vasut wrote: >>> On 2/16/24 10:10, Tomi Valkeinen wrote: >>>> Ok. Does anyone have a worry that these patches make the situation >>>> worse for the DSI case than it was before? Afaics, if the DSI lanes >>>> are not set up early enough by the DSI host, the driver would break >>>> with and without these patches. >>>> >>>> These do fix the driver for DRM_BRIDGE_ATTACH_NO_CONNECTOR and DPI, so >>>> I'd like to merge these unless these cause a regression with the DSI >>>> case. >>> >>> 1/2 looks good to me, go ahead and apply . Isn't there any way for the second patch to move forward as well though? The bridge device (under DPI to (e)DP mode) cannot really work without it, and the patches have been pending idle for a long time. =) >> >> My local patches still apply on top of 6.10-rc4, so I don't think this >> ever happened. What's still holding up this long-pending fix (at least >> for our devices)? > > Neither of the patches contains Fixes tags. If the first patch fixes an > issue in previous kernels, please consider following the stable process. > > If we are unsure about the second patch, please send the first patch > separately, adding proper tags. > Thanks Dmitry! I can send the patches again with the required fixes tags (or just patch-1 if we cannot do anything about patch-2). -- Regards Aradhya