From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.andi.de1.cc (mail.andi.de1.cc [178.238.236.174]) (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 5B8B935E54A; Thu, 18 Dec 2025 16:25:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=178.238.236.174 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766075159; cv=none; b=tJDbJ8zsbyFtdEwCwaONHpvZ/0R86b33b79+y3anvUvHwzRvprho0q8wj5k0wD7UP3+wK4A5XaPir3BQvs2RqtP1nkXaY/IzbCaD5ctj0fGjKt6jPt42l8YXevMPnbX7BAxH301hS/HwgO9GNq23B+Jv1cZaIi3PnKJKN+UIhN0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766075159; c=relaxed/simple; bh=qwJypU9bIYmExoXtAh4Yr+ZWfamC1DWgN5kEoxbDEvo=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=G2OGvPxMBdElJUq/xh2NlkZKxuuZLRA4vHMdCvwrcbQFABZnhU9a8P6oJNIoZmCr3T4SOjqCo3BKCK4zY1BImc/8jLyYocVppMnTHU7590U2S82Ce5Pkk6aARRvN/9a4/T6q6qw7avjGdzq3OWDFav1yAvgghUmAbRGVdxtTEFk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=kemnade.info; spf=pass smtp.mailfrom=kemnade.info; dkim=pass (2048-bit key) header.d=kemnade.info header.i=@kemnade.info header.b=mboMVR0c; arc=none smtp.client-ip=178.238.236.174 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=kemnade.info Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=kemnade.info Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kemnade.info header.i=@kemnade.info header.b="mboMVR0c" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kemnade.info; s=20220719; h=References:In-Reply-To:Cc:From:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID; bh=p6SJYnp842vCkHQu4i1e9JURGgkIZOc40Ucg7D58Umw=; b=mboMVR0clmVwmOkik7DJ/d1LVk GKJTXr137XbyxnXLQy/exMN+xbuxmyL0eErPsCBvcU1/yNaZm8yuJXMN2TnBUjXU692kIrag3X5HN dOoxnwA2JdeDW3ZYbUD7ln7d0b764ixHN+w11j8NrtY+sfOEZsVS8DOgcLuu6iyF81By+Nwk3oSMW jXOHvbHZHtu66FqVsDPCKCQbQ4g5dEI0K+1rASggpmwLd4u+qWD7BYWQrPsYiS52kUkv1TFv6FgAC QRhkKNcK1sUAAb7oO7PoXDCDU+KJiCVRGvIHO3foOFZmvUQZ/aIS2nTvPbmJ29hqkVyquVhreRqSI xlLsk5mw==; Date: Thu, 18 Dec 2025 16:46:20 +0100 From: Andreas Kemnade To: "Luca Ceresoli" Cc: "Kory Maincent (TI.com)" , "Jyri Sarha" , "Tomi Valkeinen" , "Maarten Lankhorst" , "Maxime Ripard" , "Thomas Zimmermann" , "David Airlie" , "Simona Vetter" , "Rob Herring" , "Krzysztof Kozlowski" , "Conor Dooley" , "Russell King" , "Bartosz Golaszewski" , "Tony Lindgren" , "Andrzej Hajda" , "Neil Armstrong" , "Robert Foss" , "Laurent Pinchart" , "Jonas Karlman" , "Jernej Skrabec" , "Markus Schneider-Pargmann" , "Bajjuri Praneeth" , "Louis Chauvet" , "Thomas Petazzoni" , "Miguel Gazquez" , , , , , Subject: Re: [PATCH v2 03/20] drm/tilcdc: Remove simulate_vesa_sync flag Message-ID: <20251218164620.40c0599d@kemnade.info> In-Reply-To: References: <20251211-feature_tilcdc-v2-0-f48bac3cd33e@bootlin.com> <20251211-feature_tilcdc-v2-3-f48bac3cd33e@bootlin.com> X-Mailer: Claws Mail 4.3.1 (GTK 3.24.49; aarch64-unknown-linux-gnu) Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 17 Dec 2025 15:20:09 +0100 "Luca Ceresoli" wrote: [...] > > Signed-off-by: Kory Maincent (TI.com) > > Code looks good. Based on your testing, which covered both boards currently > setting simulate_vesa_sync and boards not setting it: > > Reviewed-by: Luca Ceresoli > > Still it would be good to have this series, and especially this patch, > tested by someone having access to other TI boards. > Just that I do not mix up anything: grep tilcdc only gives: am335x-base0033.dts: compatible = "ti,tilcdc,slave"; am335x-guardian.dts: compatible = "ti,tilcdc,panel"; am335x-pdu001.dts: compatible = "ti,tilcdc,panel"; am335x-pepper.dts: compatible = "ti,tilcdc,panel"; am335x-sbc-t335.dts: compatible = "ti,tilcdc,panel"; am335x-sl50.dts: compatible = "ti,tilcdc,panel"; am33xx-l4.dtsi: compatible = "ti,am33xx-tilcdc"; so only am33xx affected? And no omap3/4/5. So apparently nothing I can test. @Roger: I suspect you have more of these boards than me. Regards, Andreas