From: Chris Morgan <macroalpha82@gmail.com>
To: linux-rockchip@lists.infradead.org
Cc: linux-clk@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, sebastian.reichel@collabora.com,
sboyd@kernel.org, mturquette@baylibre.com, daniel@ffwll.ch,
airlied@gmail.com, sam@ravnborg.org, neil.armstrong@linaro.org,
heiko@sntech.de, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 1/5] dt-bindings: display: panel: Update NewVision NV3051D compatibles
Date: Wed, 18 Oct 2023 11:18:44 -0500 [thread overview]
Message-ID: <20231018161848.346947-2-macroalpha82@gmail.com> (raw)
In-Reply-To: <20231018161848.346947-1-macroalpha82@gmail.com>
From: Chris Morgan <macromorgan@hotmail.com>
Update the NewVision NV3051D compatible strings by adding a new panel,
the powkiddy,rk2023-panel, and removing another entry, the
anbernic,rg353v-panel. The rg353v-panel is exactly identical to the
rg353p-panel and is not currently in use by any existing device tree.
The rk2023-panel is similar to the rg353p-panel but has slightly
different timings.
Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
---
.../devicetree/bindings/display/panel/newvision,nv3051d.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml b/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
index cce775a87f87..7a634fbc465e 100644
--- a/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
+++ b/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
@@ -21,7 +21,7 @@ properties:
- enum:
- anbernic,rg351v-panel
- anbernic,rg353p-panel
- - anbernic,rg353v-panel
+ - powkiddy,rk2023-panel
- const: newvision,nv3051d
reg: true
--
2.34.1
next prev parent reply other threads:[~2023-10-18 16:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 16:18 [PATCH 0/5] rockchip: Add Powkiddy RK2023 Chris Morgan
2023-10-18 16:18 ` Chris Morgan [this message]
2023-10-19 9:22 ` [PATCH 1/5] dt-bindings: display: panel: Update NewVision NV3051D compatibles Krzysztof Kozlowski
2023-10-19 14:50 ` Chris Morgan
2023-10-24 18:27 ` Rob Herring
2023-10-24 20:47 ` Chris Morgan
2023-10-18 16:18 ` [PATCH 2/5] drm/panel: nv3051d: Add Powkiddy RK2023 Panel Support Chris Morgan
2023-10-19 17:22 ` Jessica Zhang
2023-10-20 15:02 ` Chris Morgan
2023-10-27 22:43 ` Jessica Zhang
2023-10-18 16:18 ` [PATCH 3/5] clk: rockchip: rk3568: Add PLL rate for 115.2MHz Chris Morgan
2023-10-18 16:18 ` [PATCH 4/5] dt-bindings: arm: rockchip: Add Powkiddy RK2023 Chris Morgan
2023-10-19 9:21 ` Krzysztof Kozlowski
2023-10-19 11:35 ` Heiko Stübner
2023-10-19 14:43 ` Chris Morgan
2023-10-19 17:45 ` Heiko Stübner
2023-10-20 15:03 ` Chris Morgan
2023-10-24 15:47 ` Heiko Stübner
2023-10-25 19:17 ` Chris Morgan
2023-10-18 16:18 ` [PATCH 5/5] arm64: dts: rockchip: add " Chris Morgan
2023-10-19 8:54 ` (subset) [PATCH 0/5] rockchip: Add " Heiko Stuebner
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=20231018161848.346947-2-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sboyd@kernel.org \
--cc=sebastian.reichel@collabora.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).