From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay05.th.seeweb.it (relay05.th.seeweb.it [5.144.164.166]) (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 5D8071B6527 for ; Fri, 26 Dec 2025 14:23:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=5.144.164.166 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766758990; cv=none; b=OzU7qk7L5vcYeG+sNxF5hx03MyTckfrVtwKImKH7bdH6AnTaSzA37ttPDFxiJdCJeurAhMCSqdM82OH8YMxkkCQwfjX760MuaeGLLO/VTg3WuNWS/4T6LIQtchgoeidgt8OWIn/A91DjNUfPJmlnnbOXvtCcpUVN0l6FMJZgCaI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766758990; c=relaxed/simple; bh=gdT1EMVMcuvL149gCMzXwYKUxlWLS/RUJKDAfVcf2m8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=azGiz+IdThgBnJzdG+Nnavi/DK1/DH+XI1MvwnufyOtC1c8GkHzAd3edLvIpZwIKjWxTh+YMK2lPgIm2B2TLWGZLKfW5X2xPOsXmu+lJEgKRXYp/Euqb6/W2kXr5HS6bUNQB8vkY2L5FFntQBgJRBeCTymZgR2M9x6R+k9O0ry4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=somainline.org; spf=pass smtp.mailfrom=somainline.org; arc=none smtp.client-ip=5.144.164.166 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=somainline.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=somainline.org Received: from SoMainline.org (94-211-6-86.cable.dynamic.v4.ziggo.nl [94.211.6.86]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by m-r2.th.seeweb.it (Postfix) with ESMTPSA id 1C0C23EA6F; Fri, 26 Dec 2025 15:23:04 +0100 (CET) Date: Fri, 26 Dec 2025 15:23:02 +0100 From: Marijn Suijten To: Linus Walleij Cc: Neil Armstrong , Sam Ravnborg , David Airlie , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Andy Gross , Bjorn Andersson , Jessica Zhang , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Simona Vetter , Casey Connolly , Rob Herring , Krzysztof Kozlowski , Simona Vetter , ~postmarketos/upstreaming@lists.sr.ht, AngeloGioacchino Del Regno , Martin Botka , Jami Kettunen , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, Kuogee Hsieh , AngeloGioacchino Del Regno , Konrad Dybcio , Konrad Dybcio , Dmitry Baryshkov Subject: Re: [PATCH v2 05/11] drm/panel: Add panel driver for Samsung SOFEF01 DDIC Message-ID: References: <20251222-drm-panels-sony-v2-0-82a87465d163@somainline.org> <20251222-drm-panels-sony-v2-5-82a87465d163@somainline.org> Precedence: bulk X-Mailing-List: linux-arm-msm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On 2025-12-26 15:16:30, Marijn Suijten wrote: > On 2025-12-26 14:21:37, Linus Walleij wrote: > ... > > Only nitpicks follow: > > > > > + if (ctx->panel_type == PANEL_TYPE_TC01 || > > > + ctx->panel_type == PANEL_TYPE_UT01 || > > > + ctx->panel_type == PANEL_TYPE_UT04) { > > > + mipi_dsi_dcs_write_seq_multi(&dsi_ctx, 0xf0, 0x5a, 0x5a); > > > > The sofef00 driver tell us exactly what this sequence is: > > > > #define sofef00_test_key_on_lvl2(ctx) \ > > mipi_dsi_dcs_write_seq_multi(ctx, 0xf0, 0x5a, 0x5a) > > #define sofef00_test_key_off_lvl2(ctx) \ > > mipi_dsi_dcs_write_seq_multi(ctx, 0xf0, 0xa5, 0xa5) > > > > I would just rename these two to sofef01_test_key_on/off_lvl2() > > and use the same helpers in this driver to follow the sofef00 pattern. > > Right, yes. I think I already brought this up in V1, that some existing > Samsung drivers call this (the 0xf0 part) the MCS PASSWORD, others call it the > LEVEL_2_KEY or USER_KEY or ACCESSPROT. > > I'm curious (though should probably look up the patch history) where these names > come from, which of these names match the sofef01/03/souxp00 DDICs provided > here, and what they're supposed to mean (MCS: Magic Command Sequence?). I should have probably looked this up before asking; Manufacturer Command Sequence. Likely a generic prefix someone came up with to label commands that are not part of DCS. > Then there are possibly a lot more constants we can glean from other drivers, > though again without confirmation that it's identical on this DDIC. > > - Marijn