public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Richard Acayan <mailingradian@gmail.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 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>,
	Maxime Ripard <mripard@kernel.org>,
	 Thomas Zimmermann <tzimmermann@suse.de>,
	Thierry Reding <thierry.reding@gmail.com>,
	 Sam Ravnborg <sam@ravnborg.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	 dri-devel@lists.freedesktop.org, Yifei Zhan <yifei@zhan.science>
Subject: Re: [PATCH v3 0/5] Support for the Pixel 3a XL with the Tianma panel
Date: Mon, 27 Apr 2026 14:02:39 -0500	[thread overview]
Message-ID: <ae-yXomgNWLd8IcE@baldur> (raw)
In-Reply-To: <20260310002606.16413-1-mailingradian@gmail.com>

On Mon, Mar 09, 2026 at 08:26:01PM -0400, Richard Acayan wrote:
> This expands Pixel 3a support to the Pixel 3a XL, starting with one of
> the panel variants. The Pixel 3a XL has two variants with panels from
> Samsung or from Tianma/Novatek.
> 
> This series depends on the IMX355 front camera devicetree patches
> (https://lore.kernel.org/r/20260217002738.133534-1-mailingradian@gmail.com).

Please resubmit the DeviceTree patches once this dependency has been
resolved.

Regards,
Bjorn

> 
> Changes since v2 (https://lore.kernel.org/r/20260217000854.131242-1-mailingradian@gmail.com):
> - add support for regulator (Dmitry's review retained) (3/5)
> - use common set page function (Dmitry's review retained) (3/5)
> - squash new labels into common dtsi patch (review tags dropped) (4/5)
> - specify framebuffer in terms of memory region (4/5)
> - only specify height in XL/non-XL specific devicetrees (4/5, 5/5)
> - remove status in display devices (4/5, 5/5)
> - preserve same touchscreen physical width in sargo (4/5)
> - move entry in Makefile to correct place (5/5)
> - omit copyright year in new file (4/5)
> - correct top-of-file comment about which panel is supported (5/5)
> - explain license identifier change from GPL-2.0 to GPL-2.0-only (4/5)
> - add review tags (1/5, 3/5, 5/5)
> 
> Changes since v1 (https://lore.kernel.org/r/20260210023300.15785-1-mailingradian@gmail.com):
> - use multi functions in disable callback (3/6)
> - add and reformat comments about XL differences (5/6)
> - mention the sdc panel (6/6)
> - explain google,bonito compatible (1/6)
> - remove TODO item in code (3/6)
> - add review and testing tags (2/6, 3/6, 5/6)
> 
> Richard Acayan (5):
>   dt-bindings: arm: qcom: document google,bonito-tianma board
>   dt-bindings: panel-simple-dsi: add nt37700f compatible
>   drm/panel: Add Novatek/Tianma NT37700F panel
>   arm64: dts: qcom: sdm670-google: add common device tree include
>   arm64: dts: qcom: add support for pixel 3a xl with the tianma panel
> 
>  .../devicetree/bindings/arm/qcom.yaml         |   6 +
>  .../display/panel/panel-simple-dsi.yaml       |   2 +
>  arch/arm64/boot/dts/qcom/Makefile             |   1 +
>  .../dts/qcom/sdm670-google-bonito-tianma.dts  |  32 +
>  ...le-sargo.dts => sdm670-google-common.dtsi} |  22 +-
>  .../boot/dts/qcom/sdm670-google-sargo.dts     | 709 +-----------------
>  drivers/gpu/drm/panel/Kconfig                 |   9 +
>  drivers/gpu/drm/panel/Makefile                |   1 +
>  .../gpu/drm/panel/panel-novatek-nt37700f.c    | 299 ++++++++
>  9 files changed, 370 insertions(+), 711 deletions(-)
>  create mode 100644 arch/arm64/boot/dts/qcom/sdm670-google-bonito-tianma.dts
>  copy arch/arm64/boot/dts/qcom/{sdm670-google-sargo.dts => sdm670-google-common.dtsi} (97%)
>  create mode 100644 drivers/gpu/drm/panel/panel-novatek-nt37700f.c
> 
> -- 
> 2.53.0
> 

  parent reply	other threads:[~2026-04-27 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10  0:26 [PATCH v3 0/5] Support for the Pixel 3a XL with the Tianma panel Richard Acayan
2026-03-10  0:26 ` [PATCH v3 1/5] dt-bindings: arm: qcom: document google,bonito-tianma board Richard Acayan
2026-03-10  0:26 ` [PATCH v3 2/5] dt-bindings: panel-simple-dsi: add nt37700f compatible Richard Acayan
2026-03-10  0:26 ` [PATCH v3 3/5] drm/panel: Add Novatek/Tianma NT37700F panel Richard Acayan
2026-03-10  0:26 ` [PATCH v3 4/5] arm64: dts: qcom: sdm670-google: add common device tree include Richard Acayan
2026-03-10 12:30   ` Konrad Dybcio
2026-03-10  0:26 ` [PATCH v3 5/5] arm64: dts: qcom: add support for pixel 3a xl with the tianma panel Richard Acayan
2026-03-10 13:28 ` (subset) [PATCH v3 0/5] Support for the Pixel 3a XL with the Tianma panel Neil Armstrong
2026-04-27 19:02 ` Bjorn Andersson [this message]
2026-04-27 22:42   ` Richard Acayan

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=ae-yXomgNWLd8IcE@baldur \
    --to=andersson@kernel.org \
    --cc=airlied@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=maarten.lankhorst@linux.intel.com \
    --cc=mailingradian@gmail.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=tzimmermann@suse.de \
    --cc=yifei@zhan.science \
    /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