From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] devicetree/bindings: display: Add document for rockchip RGB output
Date: Tue, 3 Jul 2018 12:25:59 -0600 [thread overview]
Message-ID: <20180703182559.GA12809@rob-hp-laptop> (raw)
In-Reply-To: <1529997340-156879-2-git-send-email-hjc@rock-chips.com>
On Tue, Jun 26, 2018 at 03:15:39PM +0800, Sandy Huang wrote:
> This path add support rv1108 and px30 rgb output interface driver.
Bindings are for h/w, not drivers.
>
> Signed-off-by: Sandy Huang <hjc@rock-chips.com>
> Link: https://patchwork.freedesktop.org/patch/msgid/1509522765-118759-1-git-send-email-hjc at rock-chips.com
> ---
>
> Changes in v4: Add support px30
> Changes in v3: None
> Changes in v2: None
>
> .../bindings/display/rockchip/rockchip-rgb.txt | 73 ++++++++++++++++++++++
> 1 file changed, 73 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/rockchip/rockchip-rgb.txt
>
> diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip-rgb.txt b/Documentation/devicetree/bindings/display/rockchip/rockchip-rgb.txt
> new file mode 100644
> index 0000000..077b9ad
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/rockchip/rockchip-rgb.txt
> @@ -0,0 +1,73 @@
> +Rockchip RV1108 RGB interface
> +================================
> +
> +Required properties:
> +- compatible: matching the soc type:
> + - "rockchip,px30-rgb";
> + - "rockchip,rv1108-rgb";
This doesn't look right? What (and how) is getting programmed here
because you don't have any register interface.
> +
> +Optional properties:
> +- pinctrl-names: should be a "lcdc" entry or a "default" entry.
> +- pinctrl-0: pin control group to be used for this interface.
> +
> +The rgb has two video ports described by:
> + Documentation/devicetree/bindings/media/video-interfaces.txt
> +Their connections are modeled using the OF graph bindings specified in
> + Documentation/devicetree/bindings/graph.txt.
> +
> +- video port 0 for the VOP input, the remote endpoint maybe vopb/vopl/vop
So there is a mux for these inputs and they are switched with pinctrl?
Just put the pinctrl nodes of the sources and enable whichever one is
active.
Rob
next prev parent reply other threads:[~2018-07-03 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1529997340-156879-1-git-send-email-hjc@rock-chips.com>
2018-06-26 7:15 ` [PATCH v4 1/2] devicetree/bindings: display: Add document for rockchip RGB output Sandy Huang
2018-07-03 18:25 ` Rob Herring [this message]
2018-07-04 12:09 ` Sandy Huang
2018-08-27 7:11 ` Heiko Stuebner
2018-06-26 7:15 ` [PATCH v4 2/2] drm/rockchip: Add support for Rockchip Soc RGB output interface Sandy Huang
2018-06-26 11:41 ` kbuild test robot
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=20180703182559.GA12809@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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