From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Marek Vasut <marex@nabladev.com>
Cc: Maxime Ripard <mripard@kernel.org>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
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>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/panel: simple: Add timings for Raspberry Pi 7" panel
Date: Wed, 13 May 2026 19:14:44 +0300 [thread overview]
Message-ID: <553c16d9-26f9-4702-9214-02e44502af58@oss.qualcomm.com> (raw)
In-Reply-To: <faa20bc8-02d8-4715-a65d-2d8aa4102296@ideasonboard.com>
On 13/05/2026 14:52, Tomi Valkeinen wrote:
> Hi,
>
> On 23/04/2026 18:01, Tomi Valkeinen wrote:
>> Hi,
>>
>> On 23/04/2026 16:54, Marek Vasut wrote:
>>> On 4/23/26 3:16 PM, Tomi Valkeinen wrote:
>>>
>>> Hello Tomi,
>>>
>>>>>> In the past I used this panel compat instead of the
>>>>>> panel-raspberrypi-touchscreen.c and it worked.
>>>>>> IIRC Marek splitted the multi-function module into a regulator and
>>>>>> the
>>>>>> panel description.
>>>>> Ok... Indeed https://pip.raspberrypi.com/categories/651-pcn lists
>>>>> PH800480T013 as one of the panels used. Although two variants are
>>>>> listed, and also a third panel model, possibly from another vendor.
>>>>>
>>>>> My module is v1.1, and I think it has the PH800480T013-IAC21
>>>>> D/5624/ KIT- LC variant.
>>>> A question to Marek: Where did you get the timings for PH800480T013?
>>>> Did you find a datasheet?
>>> Search engine first link:
>>>
>>> https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/5337/
>>> PH800480T013-IHC09.pdf
>>
>> I tested the "powertip,ph800480t013-idf02". I'm using BeagleY-AI here,
>> and it didn't work at all. After some testing, I figured out these:
>>
>> HSW of 2 is much too small. But this could be an issue on the display
>> controller or the DSI encoder side. HWS of around 8 starts to work ok.
>> Below that, I don't get anything on the screen.
>>
>> The syncs are interesting. I set them to DISPLAY_FLAGS_VSYNC_HIGH |
>> DISPLAY_FLAGS_HSYNC_HIGH, Marek to DRM_MODE_FLAG_NVSYNC |
>> DRM_MODE_FLAG_NHSYNC. But I have sent the TC358762 series, which fixes
>> the syncs that the bridge sends (20260327-tc358762-fixes-
>> v2-0-3589d3c45f4a@ideasonboard.com).
>>
>> Flipping the syncs might explain why I used 46 and 23 as the
>> backporches, Marked used 46-hsw and 23-vsw for backporches (well,
>> Marek's vbp was off by one as I mentioned).
>>
>> But now I'm getting unsure if my TC358762 fixed the syncs correctly...
>> I'm pretty sure I measured those with my scope, though.
> I did some digging.
>
> The upstream TC358762 syncs are wrong, and inverse what they're supposed
> to be. The upstream powertip,ph800480t013-idf02 timings are such that
> the image still gets centered correctly, even with the wrong syncs, but
> this makes the timings not match the datasheet.
>
> With my TC358762 series, the syncs on the parallel bus are correct, and
> thus powertip,ph800480t013-idf02 no longer works right. My
> raspberrypi,7inch-dsi panel timings work right with the TC358762 series,
> but those panel timings have the sync polarities wrong, and thus the
> timings are also not according to the datasheet.
>
> So: we can drop this series. I'll fix the timings for
> powertip,ph800480t013-idf02, and then it'll work with the RaspberryPi 7"
> DSI display module...
Ack, thanks for your updates.
--
With best wishes
Dmitry
prev parent reply other threads:[~2026-05-13 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 13:13 [PATCH 0/2] drm/panel: Add Raspberry Pi 7" panel Tomi Valkeinen
2026-04-20 13:13 ` [PATCH 1/2] dt-bindings: display: simple: Add Raspberry Pi 7" DSI Display module panel Tomi Valkeinen
2026-04-20 16:01 ` Conor Dooley
2026-04-20 13:13 ` [PATCH 2/2] drm/panel: simple: Add timings for Raspberry Pi 7" panel Tomi Valkeinen
2026-04-22 19:22 ` Dmitry Baryshkov
2026-04-23 12:01 ` Tomi Valkeinen
2026-04-23 12:14 ` Maxime Ripard
2026-04-23 12:28 ` Tomi Valkeinen
2026-04-23 12:33 ` Dmitry Baryshkov
2026-04-23 13:13 ` Tomi Valkeinen
2026-04-23 13:16 ` Tomi Valkeinen
2026-04-23 13:54 ` Marek Vasut
2026-04-23 14:05 ` Tomi Valkeinen
2026-04-23 15:01 ` Tomi Valkeinen
2026-05-13 11:52 ` Tomi Valkeinen
2026-05-13 16:14 ` Dmitry Baryshkov [this message]
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=553c16d9-26f9-4702-9214-02e44502af58@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@nabladev.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ideasonboard.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