From: Archit Taneja <architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Bjorn Andersson <bjorn-UYDU3/A3LUY@public.gmane.org>
Cc: Andy Gross <agross-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
linux-arm-msm
<linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] dt-bindings: drm/msm: Update bindings for MDP5
Date: Mon, 19 Oct 2015 11:19:06 +0530 [thread overview]
Message-ID: <56248452.6060509@codeaurora.org> (raw)
In-Reply-To: <CAJAp7OhSLFHAdg9POwfhFRU2NmYS8Oc-Zpn8-UCdLfpBWepbdw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 10/18/2015 08:49 AM, Bjorn Andersson wrote:
> On Fri, Oct 16, 2015 at 5:06 AM, Archit Taneja <architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> wrote:
>> MDP5 has a different compatible string (which causes checkpatch warnings
>> when we try to add MDP5 device nodes). It also has different list of
>> clocks.
>>
>> Update the bindings for MDP5.
>>
>> Signed-off-by: Archit Taneja <architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
>> ---
>> Documentation/devicetree/bindings/drm/msm/mdp.txt | 23 ++++++++++++++++-------
>> 1 file changed, 16 insertions(+), 7 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/drm/msm/mdp.txt b/Documentation/devicetree/bindings/drm/msm/mdp.txt
>> index 1a0598e..e926daa 100644
>> --- a/Documentation/devicetree/bindings/drm/msm/mdp.txt
>> +++ b/Documentation/devicetree/bindings/drm/msm/mdp.txt
>> @@ -3,18 +3,27 @@ Qualcomm adreno/snapdragon display controller
>> Required properties:
>> - compatible:
>> * "qcom,mdp" - mdp4
>> + * "qcom,mdss_mdp" - mdp5
>
> Wouldn't it be better to name these "qcom,mdp4" and "qcom,mdp5" so
> that we don't have to rely on some magic detection mechanism to
> support future versions?
My guess is that compatibility string "mdss_mdp" came from the
downstream kernels. Chips having MDP4 were supported on downstream
kernels that preceded DT.
Since we don't have any MDP DT upstream, I think we could go with the
string names you suggested. It might break things for people who might
try to use an old downstream dts file with a new kernel. But that
doesn't sound like the worst thing.
Archit
>
> Regards,
> Bjorn
>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-19 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 12:06 [PATCH 1/2] dt-bindings: drm/msm: Update bindings for MDP5 Archit Taneja
2015-10-16 12:06 ` [PATCH 2/2] arm64: dtsi: Add device nodes for GPU and MDSS on MSM8916 Archit Taneja
2015-10-18 3:19 ` [PATCH 1/2] dt-bindings: drm/msm: Update bindings for MDP5 Bjorn Andersson
[not found] ` <CAJAp7OhSLFHAdg9POwfhFRU2NmYS8Oc-Zpn8-UCdLfpBWepbdw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-19 5:49 ` Archit Taneja [this message]
2015-10-20 18:17 ` Rob Clark
2015-10-23 7:47 ` Archit Taneja
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=56248452.6060509@codeaurora.org \
--to=architt-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=agross-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=bjorn-UYDU3/A3LUY@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).