From: Robert Foss <robert.foss@linaro.org>
To: andrzej.hajda@intel.com, narmstrong@baylibre.com,
robert.foss@linaro.org, Laurent.pinchart@ideasonboard.com,
jonas@kwiboo.se, jernej.skrabec@gmail.com, airlied@linux.ie,
daniel@ffwll.ch, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dianders@chromium.org,
lkundrak@v3.sk, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Morgan <macromorgan@hotmail.com>,
tzimmermann@suse.de, javierm@redhat.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org
Subject: [PATCH v1 1/2] Revert "dt-bindings: Add byteswap order to chrontel ch7033"
Date: Mon, 12 Sep 2022 13:38:57 +0200 [thread overview]
Message-ID: <20220912113856.817188-2-robert.foss@linaro.org> (raw)
In-Reply-To: <20220912113856.817188-1-robert.foss@linaro.org>
As reported by Laurent in response to this commit[1], this functionality should
not be implemented using the devicetree, because of this let's revert this series
for now.
This reverts commit a4be71430c76eca43679e8485085c230afa84460.
[1] https://lore.kernel.org/all/20220902153906.31000-2-macroalpha82@gmail.com/
Signed-off-by: Robert Foss <robert.foss@linaro.org>
---
.../bindings/display/bridge/chrontel,ch7033.yaml | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml b/Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml
index 984b90893583..bb6289c7d375 100644
--- a/Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml
+++ b/Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml
@@ -14,19 +14,6 @@ properties:
compatible:
const: chrontel,ch7033
- chrontel,byteswap:
- $ref: /schemas/types.yaml#/definitions/uint8
- enum:
- - 0 # BYTE_SWAP_RGB
- - 1 # BYTE_SWAP_RBG
- - 2 # BYTE_SWAP_GRB
- - 3 # BYTE_SWAP_GBR
- - 4 # BYTE_SWAP_BRG
- - 5 # BYTE_SWAP_BGR
- description: |
- Set the byteswap value of the bridge. This is optional and if not
- set value of BYTE_SWAP_BGR is used.
-
reg:
maxItems: 1
description: I2C address of the device
--
2.34.1
next prev parent reply other threads:[~2022-09-12 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 11:38 [PATCH v1 0/2] Revert chrontel-ch7033 byteswap order series Robert Foss
2022-09-12 11:38 ` Robert Foss [this message]
2022-09-13 15:49 ` [PATCH v1 1/2] Revert "dt-bindings: Add byteswap order to chrontel ch7033" Rob Herring
2022-09-12 11:38 ` [PATCH v1 2/2] Revert "drm/bridge: ti-sn65dsi86: Implement bridge connector operations for DP" Robert Foss
2022-09-12 14:29 ` Doug Anderson
2022-09-12 14:42 ` Laurent Pinchart
2022-09-15 10:32 ` Robert Foss
2022-09-12 12:33 ` [PATCH v1 0/2] Revert chrontel-ch7033 byteswap order series Laurent Pinchart
2022-09-12 21:35 ` Chris Morgan
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=20220912113856.817188-2-robert.foss@linaro.org \
--to=robert.foss@linaro.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=maarten.lankhorst@linux.intel.com \
--cc=macromorgan@hotmail.com \
--cc=mripard@kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).