From: Archit Taneja <architt@codeaurora.org>
To: Rob Clark <robdclark@gmail.com>
Cc: Bjorn Andersson <bjorn@kryo.se>,
Andy Gross <agross@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: drm/msm: Update bindings for MDP5
Date: Fri, 23 Oct 2015 13:17:34 +0530 [thread overview]
Message-ID: <5629E616.1090601@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGsyN_FNXGO+SrM6SFQJA7jtCnVBjcCdYqVWgQ23-fH+ZQ@mail.gmail.com>
On 10/20/2015 11:47 PM, Rob Clark wrote:
> On Mon, Oct 19, 2015 at 1:49 AM, Archit Taneja <architt@codeaurora.org> wrote:
>>
>> On 10/18/2015 08:49 AM, Bjorn Andersson wrote:
>>>
>>> On Fri, Oct 16, 2015 at 5:06 AM, Archit Taneja <architt@codeaurora.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@codeaurora.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.
>
> it would break things for downstream 3.10/mdp5 dt files.. but what
> I'd suggest is to make the code look for both qcom,mdp5 and
> qcom,mdss_mdp but only document the former
That's a good idea. I'll update the patches to do that.
Archit
>
> BR,
> -R
>
>> Archit
>>
>>>
>>> Regards,
>>> Bjorn
>>>
>>
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
>> hosted by The Linux Foundation
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-10-23 7:47 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
2015-10-20 18:17 ` Rob Clark
2015-10-23 7:47 ` Archit Taneja [this message]
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=5629E616.1090601@codeaurora.org \
--to=architt@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn@kryo.se \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.