From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>
Cc: thierry.reding@gmail.com, sam@ravnborg.org, airlied@linux.ie,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, jonathanh@nvidia.com,
arnd@arndb.de, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: display: Add bindings for JDI LPM102A188A
Date: Fri, 30 Sep 2022 12:49:31 +0200 [thread overview]
Message-ID: <efa2f644-0a1d-00f7-970c-f17ceb0cc550@linaro.org> (raw)
In-Reply-To: <20220929170502.1034040-2-diogo.ivo@tecnico.ulisboa.pt>
On 29/09/2022 19:04, Diogo Ivo wrote:
> The LPM102A188A is a 10.2" 2560x1800 IPS panel found in
> the Google Pixel C.
>
Thank you for your patch. There is something to discuss/improve.
> + Each of the DSI channels controls a separate DSI peripheral. The peripheral
> + driven by the first link (DSI-LINK1) is considered the primary peripheral
> + and controls the device. The 'link2' property contains a phandle to the
> + peripheral driven by the second link (DSI-LINK2).
> +
> +allOf:
> + - $ref: panel-common.yaml#
> +
> +properties:
> + compatible:
> + const: jdi,lpm102a188a
> +
> + reg: true
> + enable-gpios: true
> + reset-gpios: true
> + power-supply: true
> + backlight: true
> +
> + ts-reset-gpios:
> + maxItems: 1
> + description: |
> + Specifier for a GPIO connected to the touchscreen reset control signal.
> + The reset signal is active low.
Isn't touchscreen a separate (input) device?
> +
> + ddi-supply:
> + description: The regulator that provides IOVCC (1.8V).
> +
> + link2:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: |
> + phandle to the DSI peripheral on the secondary link. Note that the
> + presence of this property marks the containing node as DSI-LINK1.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-30 11:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 17:04 [PATCH 0/4] Add JDI LPM102A188A display panel support Diogo Ivo
2022-09-29 17:04 ` [PATCH 1/4] dt-bindings: display: Add bindings for JDI LPM102A188A Diogo Ivo
2022-09-30 10:49 ` Krzysztof Kozlowski [this message]
2022-10-03 17:06 ` Diogo Ivo
2022-10-04 11:05 ` Krzysztof Kozlowski
2022-10-04 16:37 ` Diogo Ivo
2022-09-29 17:05 ` [PATCH 2/4] drm/tegra: dsi: Clear enable register if powered by bootloader Diogo Ivo
2022-09-30 11:11 ` Thierry Reding
2022-10-03 18:13 ` Diogo Ivo
2022-09-29 17:05 ` [PATCH 3/4] drm/panel: Add driver for JDI LPM102A188A Diogo Ivo
2022-09-29 17:05 ` [PATCH 4/4] arm64: dts: smaug: Add display panel node Diogo Ivo
2022-09-30 10:51 ` Krzysztof Kozlowski
2022-09-30 11:15 ` Thierry Reding
2022-09-30 11:20 ` Krzysztof Kozlowski
2022-09-30 21:14 ` Rob Herring
2022-10-01 9:53 ` Krzysztof Kozlowski
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=efa2f644-0a1d-00f7-970c-f17ceb0cc550@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@tecnico.ulisboa.pt \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/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).