From: Thierry Reding <thierry.reding@gmail.com>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: neil.armstrong@linaro.org, sam@ravnborg.org, airlied@gmail.com,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Add JDI LPM102A188A display panel support
Date: Wed, 16 Aug 2023 18:30:41 +0200 [thread overview]
Message-ID: <ZNz5sSnxs_E8p_4J@orome> (raw)
In-Reply-To: <20230807133307.27456-1-diogo.ivo@tecnico.ulisboa.pt>
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
On Mon, Aug 07, 2023 at 02:33:00PM +0100, Diogo Ivo wrote:
> Hello,
>
> These patches add support for the JDI LPM102A188A display panel,
> found in the Google Pixel C.
>
> Patch 1 adds the DT bindings for the panel.
>
> Patch 2 adds the panel driver, which is based on the downstream
> kernel driver published by Google and developed by Sean Paul.
>
> Patches 3-5 add DT nodes for the regulator, backlight controller and
> display panel.
>
> The first version of this patch series can be found at:
> https://lore.kernel.org/all/20220929170502.1034040-1-diogo.ivo@tecnico.ulisboa.pt/
>
> The first submission of v2 can be found at:
> https://lore.kernel.org/all/20221025153746.101278-1-diogo.ivo@tecnico.ulisboa.pt/
>
> Changes in v2:
> - Patch 1: remove touchscreen reset gpio property
> - Patch 2: clear register based on its value rather than a DT property
> - Patch 3: tune backlight delay values
> - Patch 4: add generic node names, remove underscores
>
> Changes in v3:
> - Patch 1: add Reviewed-by
> - Patch 2: fix error handling, remove enabled/prepared booleans, add
> dc/dc setting
> - Patches 3-5: Split previous patch 3 into three different patches,
> each adding a separate node
> - removed previous patch 2 pertaining to Tegra DSI reset as it was upstreamed
>
> Diogo Ivo (5):
> dt-bindings: display: Add bindings for JDI LPM102A188A
> drm/panel: Add driver for JDI LPM102A188A
> arm64: dts: smaug: Add DSI/CSI regulator
> arm64: dts: smaug: Add backlight node
> arm64: dts: smaug: Add display panel node
I've picked up patches 3-5 into the Tegra tree and I assume the other
two will go in through drm-misc?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-16 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 13:33 [PATCH v3 0/5] Add JDI LPM102A188A display panel support Diogo Ivo
2023-08-07 13:33 ` [PATCH v3 3/5] arm64: dts: smaug: Add DSI/CSI regulator Diogo Ivo
2023-08-07 13:33 ` [PATCH v3 4/5] arm64: dts: smaug: Add backlight node Diogo Ivo
2023-08-07 13:33 ` [PATCH v3 5/5] arm64: dts: smaug: Add display panel node Diogo Ivo
2023-08-16 16:29 ` (subset) [PATCH v3 0/5] Add JDI LPM102A188A display panel support Thierry Reding
2023-08-16 16:30 ` Thierry Reding [this message]
2023-08-16 16:57 ` neil.armstrong
2023-08-16 16:56 ` (subset) " Neil Armstrong
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=ZNz5sSnxs_E8p_4J@orome \
--to=thierry.reding@gmail.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@tecnico.ulisboa.pt \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
/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