From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: krzysztof.kozlowski+dt@linaro.org, jonas@kwiboo.se,
airlied@linux.ie, robert.foss@linaro.org,
narmstrong@baylibre.com, Chris Morgan <macromorgan@hotmail.com>,
dri-devel@lists.freedesktop.org, lkundrak@v3.sk,
andrzej.hajda@intel.com, robh+dt@kernel.org,
jernej.skrabec@gmail.com
Subject: Re: [PATCH V2 1/2] dt-bindings: Add byteswap order to chrontel ch7033
Date: Sat, 3 Sep 2022 03:17:23 +0300 [thread overview]
Message-ID: <YxKdE7ZQ97NsuqZk@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20220902153906.31000-2-macroalpha82@gmail.com>
Hi Chris,
Thank you for the patch.
On Fri, Sep 02, 2022 at 10:39:05AM -0500, Chris Morgan wrote:
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Update dt-binding documentation to add support for setting byteswap of
> chrontel ch7033.
>
> New property name of chrontel,byteswap added to set the byteswap order.
> This property is optional.
>
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
> Reviewed-by: Robert Foss <robert.foss@linaro.org>
> ---
> .../bindings/display/bridge/chrontel,ch7033.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml b/Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml
> index bb6289c7d375..984b90893583 100644
> --- a/Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml
> +++ b/Documentation/devicetree/bindings/display/bridge/chrontel,ch7033.yaml
> @@ -14,6 +14,19 @@ 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.
I don't think this belongs to the device tree. The source of data
connected to the CH7033 input could use different formats. This
shouldn't be hardcoded, but queried at runtime, using the input and
output media bus formats infrastructure that the DRM bridge framework
includes.
> +
> reg:
> maxItems: 1
> description: I2C address of the device
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-09-03 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 15:39 [PATCH V2 0/2] chrontel-ch7033: Add byteswap order option Chris Morgan
2022-09-02 15:39 ` [PATCH V2 1/2] dt-bindings: Add byteswap order to chrontel ch7033 Chris Morgan
2022-09-03 0:17 ` Laurent Pinchart [this message]
2022-09-05 15:20 ` Robert Foss
2022-09-07 13:29 ` Chris Morgan
2022-09-07 20:21 ` Laurent Pinchart
2022-09-02 15:39 ` [PATCH V2 2/2] drm/bridge: chrontel-ch7033: Add byteswap order setting Chris Morgan
2022-09-03 0:14 ` Laurent Pinchart
2022-09-02 16:21 ` [PATCH V2 0/2] chrontel-ch7033: Add byteswap order option Robert Foss
2022-09-03 0:18 ` Laurent Pinchart
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=YxKdE7ZQ97NsuqZk@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lkundrak@v3.sk \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=narmstrong@baylibre.com \
--cc=robert.foss@linaro.org \
--cc=robh+dt@kernel.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