From: Archit Taneja <architt@codeaurora.org>
To: robdclark@gmail.com
Cc: linux-arm-msm@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 3/6] dt-bindings: drm/msm: Update MDP bindings
Date: Wed, 18 Nov 2015 20:56:00 +0530 [thread overview]
Message-ID: <564C9888.9020703@codeaurora.org> (raw)
In-Reply-To: <1447845547-6801-4-git-send-email-architt@codeaurora.org>
+dt list
On 11/18/2015 4:49 PM, Archit Taneja wrote:
> Update DT bindings for mdp. We now have a more uniform and future-proof
> set of compatible strings.
>
> MDP5 bindings were missing. Add those and update details on the
> clock-names properties.
>
> Signed-off-by: Archit Taneja <architt@codeaurora.org>
> ---
> .../devicetree/bindings/display/msm/mdp.txt | 26 +++++++++++++++-------
> 1 file changed, 18 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/msm/mdp.txt b/Documentation/devicetree/bindings/display/msm/mdp.txt
> index 0833eda..a214f6c 100644
> --- a/Documentation/devicetree/bindings/display/msm/mdp.txt
> +++ b/Documentation/devicetree/bindings/display/msm/mdp.txt
> @@ -2,18 +2,28 @@ Qualcomm adreno/snapdragon display controller
>
> Required properties:
> - compatible:
> - * "qcom,mdp" - mdp4
> + * "qcom,mdp4" - mdp4
> + * "qcom,mdp5" - mdp5
> - reg: Physical base address and length of the controller's registers.
> - interrupts: The interrupt signal from the display controller.
> - connectors: array of phandles for output device(s)
> - clocks: device clocks
> See ../clocks/clock-bindings.txt for details.
> -- clock-names: the following clocks are required:
> - * "core_clk"
> - * "iface_clk"
> - * "src_clk"
> - * "hdmi_clk"
> - * "mpd_clk"
> +- clock-names: the following clocks are required.
> + For MDP4:
> + * "core_clk"
> + * "iface_clk"
> + * "lut_clk"
> + * "src_clk"
> + * "hdmi_clk"
> + * "mdp_clk"
> + For MDP5:
> + * "bus_clk"
> + * "iface_clk"
> + * "core_clk_src"
> + * "core_clk"
> + * "lut_clk" (some MDP5 versions may not need this)
> + * "vsync_clk"
>
> Optional properties:
> - gpus: phandle for gpu device
> @@ -26,7 +36,7 @@ Example:
> ...
>
> mdp: qcom,mdp@5100000 {
> - compatible = "qcom,mdp";
> + compatible = "qcom,mdp4";
> reg = <0x05100000 0xf0000>;
> interrupts = <GIC_SPI 75 0>;
> connectors = <&hdmi>;
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-11-18 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 11:19 [PATCH 0/6] drm/msm: Work only with DT supported kernels Archit Taneja
2015-11-18 11:19 ` [PATCH 1/6] drm/msm: Remove non-DT code in msm_drv Archit Taneja
2015-11-18 11:19 ` [PATCH 2/6] drm/msm: Update compatible strings for mdp Archit Taneja
2015-11-18 11:19 ` [PATCH 3/6] dt-bindings: drm/msm: Update MDP bindings Archit Taneja
2015-11-18 15:26 ` Archit Taneja [this message]
2015-11-18 11:19 ` [PATCH 4/6] drm/msm/mdp: Remove CONFIG_OF checks from MDP drivers Archit Taneja
2015-11-18 11:19 ` [PATCH 5/6] drm/msm/hdmi: remove CONFIG_OF checks Archit Taneja
2015-11-18 11:19 ` [PATCH 6/6] drm/msm/adreno: Remove " Archit Taneja
2015-11-18 14:45 ` Rob Clark
2015-11-18 16:04 ` Archit Taneja
2015-11-18 20:29 ` Rob Clark
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=564C9888.9020703@codeaurora.org \
--to=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.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