From: Sandy Huang <hjc@rock-chips.com>
To: Rob Herring <robh@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Mark Yao <mark.yao@rock-chips.com>
Subject: Re: [PATCH 1/3] dt-bindings: Add document for rockchip RGB output interface
Date: Wed, 20 Sep 2017 10:57:29 +0800 [thread overview]
Message-ID: <6cd1ac0d-bc99-f8f3-15da-799f8623ce65@rock-chips.com> (raw)
In-Reply-To: <d631ff56-e3e6-688f-d9b6-a7101ce047d5@rock-chips.com>
在 2017/9/20 9:51, Sandy Huang 写道:
> Hi rob,
> thanks for you review.
>
> 在 2017/9/19 22:46, Rob Herring 写道:
>> On Thu, Sep 14, 2017 at 11:43:18AM +0800, Sandy Huang wrote:
>>> This path add support rv1108 rgb output interface driver.
>>>
>>> Signed-off-by: Sandy Huang <hjc@rock-chips.com>
>>> ---
>>> .../bindings/display/rockchip/rockchip-rgb.txt | 80
>>> ++++++++++++++++++++++
>>> 1 file changed, 80 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..4164512
>>> --- /dev/null
>>> +++
>>> b/Documentation/devicetree/bindings/display/rockchip/rockchip-rgb.txt
>>> @@ -0,0 +1,80 @@
>>> +Rockchip RV1108 RGB interface
>>> +================================
>>> +
>>> +Required properties:
>>> +- compatible: matching the soc type:
>>> + - "rockchip,rv1108-rgb";
>>> +
>>> +Optional properties:
>>> +- pinctrl-names: must contain a "lcdc" entry.
>>> +- pinctrl-0: pin control group to be used for this interface.
>>> +
>>> +Required nodes:
>>> +- rockchip,rgb-mode: should be "p888", "p666", "p565", "s888",
>>> "s888-dummy"
>>
>> This should be a standard property. Any device with a parallel interface
>> is going to need something like this.
>>
> so, i need to move this property to panel? or just rename
> rockchip,rgb-mode to rgb-mode?
>
>>> + - p888: output r8-g8-b8 at each dclk cycle for per-pixel
>>> + - p666: output r6-g6-b6 at each dclk cycle for per-pixel
>>> + - p565: output r5-g6-b5 at each dclk cycle for per-pixel
>>> + - s888: output r8-g8-b8 in three dclk cycle for per-pixel
>>> + - s888-dmmy: output r8-g8-b8-dummy in four dclk cycle for per-pixel
>>> +
>>> +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
>>> +- video port 1 for either a panel or subsequent encoder
>>> +
>>> +the panel described by:
>>> + Documentation/devicetree/bindings/display/panel/simple-panel.txt
>>> +Panel other required properties:
>>> +- ports for remote rgb output.
>>> +
>>> +Example:
>>> +
>>> +panel: panel {
>>> + compatible = "auo,b101ean01";
>>> + enable-gpios = <&gpio7 21 GPIO_ACTIVE_HIGH>;
>>> +
>>> + ports {
>>> + panel_in_rgb: endpoint {
>>> + remote-endpoint = <&rgb_out_panel>;
>>> + };
>>> + };
>>> +};
>>> +
>>> +For Rockchip RV1108:
>>> +
>>> + rgb: rgb {
>>> + compatible = "rockchip,rv1108-rgb";
>>> + pinctrl-names = "lcdc";
>>> + pinctrl-0 = <&lcdc_ctl>;
>>> + rockchip,rgb-mode = "p888";
>>> +
>>> + ports {
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + rgb_in: port@0 {
>>> + reg = <0>;
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + rgb_in_vop: endpoint@0 {
>>> + reg = <0>;
>>
>> Don't need reg for a single endpoint.
>>
> ok, this will be deleted at next version.
>>> + remote-endpoint = <&vop_out_rgb>;
>>> + };
>>> + };
>>> +
>>> + rgb_out: port@1 {
>>> + reg = <1>;
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + rgb_out_panel: endpoint@0 {
>>> + reg = <0>;
>>
>> ditto.
>>
> ok, this will be deleted at next version.
sorry,this can't be deleted, because rgb output remote endpoint maybe
panel or convert chip, the dts node maybe like this:
panel: panel {
status = "disabled";
ports {
panel_in_rgb: endpoint {
remote-endpoint = <&rgb_out_panel>;
};
};
};
bridge: bridge {
status = "okay";
ports {
bridge_in_rgb: endpoint {
remote-endpoint = <&rgb_out_bridge>;
};
};
};
rgb_out: port@1 {
reg = <1>;
#address-cells = <1>;
#size-cells = <0>;
rgb_out_panel: endpoint@0 {
reg = <0>;
remote-endpoint = <&panel_in_rgb>;
};
rgb_out_bridge: endpoint@1 {
reg = <1>;
remote-endpoint = <&bridge_in_rgb>;
};
};
so rockchip_rgb_bind() @ rockchip_rgb.c use reg id to find the remote
actived endpoint.
for_each_child_of_node(port, endpoint) {
of_property_read_u32(endpoint, "reg", &endpoint_id);
ret = drm_of_find_panel_or_bridge(dev->of_node, 1, endpoint_id,
&rgb->panel, &rgb->bridge);
if (!ret)
break;
}
>>> + remote-endpoint = <&panel_in_rgb>;
>>> + };
>>> + };
>>> + };
>>> + };
>>> --
>>> 2.7.4
>>>
>>>
>>
>>
>>
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2017-09-20 2:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 3:43 [PATCH 0/3] Add support " Sandy Huang
2017-09-14 3:43 ` [PATCH 1/3] dt-bindings: Add document for " Sandy Huang
2017-09-19 14:46 ` Rob Herring
2017-09-20 1:51 ` Sandy Huang
2017-09-20 2:57 ` Sandy Huang [this message]
2017-09-21 19:40 ` Rob Herring
2017-09-22 2:59 ` Sandy Huang
2017-09-14 3:43 ` [PATCH 2/3] drm/rockchip: Add support for Rockchip Soc " Sandy Huang
2017-09-19 23:02 ` Sean Paul
2017-09-20 3:03 ` Sandy Huang
2017-09-14 3:43 ` [PATCH 3/3] drm/rockchip: vop: Add more RGB output interface type Sandy Huang
2017-09-19 23:03 ` Sean Paul
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=6cd1ac0d-bc99-f8f3-15da-799f8623ce65@rock-chips.com \
--to=hjc@rock-chips.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mark.yao@rock-chips.com \
--cc=robh@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
all inboxes | Powered by JetHome®