From: David Heidelberg <david@ixit.cz>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Casey Connolly <casey.connolly@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v3 4/8] drm/panel: Add Samsung S6E3FC2X01 DDIC with AMS641RW panel
Date: Thu, 16 Oct 2025 22:46:56 +0200 [thread overview]
Message-ID: <d13cdf83-22df-4a24-a711-2db4abe3a0a8@ixit.cz> (raw)
In-Reply-To: <didkbltadu4ql6xcqtjrtf2iguody5bgy6mqlwtbyfgbambaii@mzofzymnfbju>
On 16/10/2025 22:12, Dmitry Baryshkov wrote:
> On Thu, Oct 16, 2025 at 06:16:59PM +0200, David Heidelberg via B4 Relay wrote:
>> From: David Heidelberg <david@ixit.cz>
>>
>> Add panel driver used in the OnePlus 6T.
>>
>> No datasheet, based mostly on EDK2 init sequence and the downstream driver.
>>
>> Note: This driver doesn't use previously mentioned "samsung,s6e3fc2x01"
>> by OnePlus 6T device-tree.
>> The reason is because DDIC itself without knowing the panel type used
>> with it will not give the driver enough information about the panel used,
>> as the panel cannot be autodetected.
>> While would be more practical to support the original compatible,
>> I would like to avoid it, to prevent confusing devs upstreaming DDICs.
>>
>> Based on work of:
>> Casey Connolly <casey@connolly.tech>
>> Joel Selvaraj <foss@joelselvaraj.com>
>> Nia Espera <a5b6@riseup.net>
>>
>> Signed-off-by: David Heidelberg <david@ixit.cz>
>> ---
>> MAINTAINERS | 1 +
>> drivers/gpu/drm/panel/Kconfig | 13 +
>> drivers/gpu/drm/panel/Makefile | 1 +
>> drivers/gpu/drm/panel/panel-samsung-s6e3fc2x01.c | 399 +++++++++++++++++++++++
>> 4 files changed, 414 insertions(+)
>>
>> +
>> +static const struct drm_display_mode ams641rw_mode = {
>> + .clock = (1080 + 72 + 16 + 36) * (2340 + 32 + 4 + 18) * 60 / 1000,
>> + .hdisplay = 1080,
>> + .hsync_start = 1080 + 72,
>> + .hsync_end = 1080 + 72 + 16,
>> + .htotal = 1080 + 72 + 16 + 36,
>> + .vdisplay = 2340,
>> + .vsync_start = 2340 + 32,
>> + .vsync_end = 2340 + 32 + 4,
>> + .vtotal = 2340 + 32 + 4 + 18,
>> + .width_mm = 68,
>> + .height_mm = 145,
>> +};
>> +
>> +static int s6e3fc2x01_get_modes(struct drm_panel *panel,
>> + struct drm_connector *connector)
>> +{
>> + struct drm_display_mode *mode;
>> +
>> + mode = drm_mode_duplicate(connector->dev, &ams641rw_mode);
>> + if (!mode)
>> + return -ENOMEM;
>> +
>> + drm_mode_set_name(mode);
>> +
>> + mode->type = DRM_MODE_TYPE_DRIVER | DRM_MODE_TYPE_PREFERRED;
>> + connector->display_info.width_mm = mode->width_mm;
>> + connector->display_info.height_mm = mode->height_mm;
>> + drm_mode_probed_add(connector, mode);
>
> drm_connector_helper_get_modes_fixed()
Thanks, next version will have it.>
>> +
>> + return 1;
>> +}
>> +
>> +
>> +static const struct of_device_id s6e3fc2x01_of_match[] = {
>> + /* samsung,s6e3fc2x01 will default to the AMS641RW mode (legacy) */
>> + { .compatible = "samsung,s6e3fc2x01", .data = &ams641rw_mode },
>
> Is there a need to probide this kind of legacy?
I don't know. I don't see the need to provide it, but I understood you
may want to have it. If not, please tell me and I'll happily remove it
from next version.
David
>
>> + { .compatible = "samsung,s6e3fc2x01-ams641rw", .data = &ams641rw_mode },
>> + { /* sentinel */ }
>> +};
>> +MODULE_DEVICE_TABLE(of, s6e3fc2x01_of_match);
>> +
>
--
David Heidelberg
next prev parent reply other threads:[~2025-10-16 20:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 16:16 [PATCH v3 0/8] Add OnePlus 6T display (Samsung S6E3FC2X01 DDIC with AMS641RW panel) David Heidelberg via B4 Relay
2025-10-16 16:16 ` [PATCH v3 1/8] dt-bindings: panel: Add Samsung S6E3FC2X01 DDIC with panel David Heidelberg via B4 Relay
2025-10-16 16:16 ` [PATCH v3 2/8] arm64: dts: qcom: sdm845-oneplus: Describe panel vci and poc supplies David Heidelberg via B4 Relay
2025-10-16 20:08 ` Dmitry Baryshkov
2025-10-20 13:45 ` Casey Connolly
2025-10-20 14:03 ` David Heidelberg
2025-10-16 16:16 ` [PATCH v3 3/8] arm64: dts: qcom: sdm845-oneplus-fajita: Compatible describing both DDIC and panel David Heidelberg via B4 Relay
2025-10-16 20:09 ` Dmitry Baryshkov
2025-10-16 16:16 ` [PATCH v3 4/8] drm/panel: Add Samsung S6E3FC2X01 DDIC with AMS641RW panel David Heidelberg via B4 Relay
2025-10-16 20:12 ` Dmitry Baryshkov
2025-10-16 20:46 ` David Heidelberg [this message]
2025-10-19 12:11 ` Dmitry Baryshkov
2025-10-16 16:17 ` [PATCH v3 5/8] arm64: dts: qcom: sdm845-oneplus: Group panel pinctrl David Heidelberg via B4 Relay
2025-10-16 20:12 ` Dmitry Baryshkov
2025-10-16 16:17 ` [PATCH v3 6/8] arm64: dts: qcom: sdm845-oneplus: Implement panel sleep pinctrl David Heidelberg via B4 Relay
2025-10-16 20:13 ` Dmitry Baryshkov
2025-10-16 16:17 ` [PATCH v3 7/8] arm64: dts: qcom: sdm845-oneplus: Describe TE gpio David Heidelberg via B4 Relay
2025-10-16 20:15 ` Dmitry Baryshkov
2025-10-16 21:00 ` David Heidelberg
2025-10-16 16:17 ` [PATCH v3 8/8] dt-bindings: display: panel-simple-dsi: Remove Samsung S6E3FC2 compatible David Heidelberg via B4 Relay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d13cdf83-22df-4a24-a711-2db4abe3a0a8@ixit.cz \
--to=david@ixit.cz \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).