All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen He <wen.he_1@nxp.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: "linux-devel@linux.nxdi.nxp.com" <linux-devel@linux.nxdi.nxp.com>,
	Liviu Dudau <liviu.dudau@arm.com>,
	Brian Starkey <brian.starkey@arm.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Mark Rutland <mark.rutland@arm.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Leo Li <leoyang.li@nxp.com>
Subject: RE: [EXT] Re: [v3 1/2] dt/bindings: display: Add optional property node for Mali DP500
Date: Mon, 19 Aug 2019 02:13:39 +0000	[thread overview]
Message-ID: <DB7PR04MB5195A94A64615FF44C0F4442E2A80@DB7PR04MB5195.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAL_JsqLPZ+hCGd=J3MU83saHJJ-yx6k+X0Y7-2ECu5yT8PxF4w@mail.gmail.com>



> -----Original Message-----
> From: Rob Herring <robh+dt@kernel.org>
> Sent: 2019年8月17日 4:09
> To: Wen He <wen.he_1@nxp.com>
> Cc: linux-devel@linux.nxdi.nxp.com; Liviu Dudau <liviu.dudau@arm.com>;
> Brian Starkey <brian.starkey@arm.com>; David Airlie <airlied@linux.ie>; Daniel
> Vetter <daniel@ffwll.ch>; Mark Rutland <mark.rutland@arm.com>; dri-devel
> <dri-devel@lists.freedesktop.org>; devicetree@vger.kernel.org;
> linux-kernel@vger.kernel.org; Leo Li <leoyang.li@nxp.com>
> Subject: [EXT] Re: [v3 1/2] dt/bindings: display: Add optional property node for
> Mali DP500
> 
> Caution: EXT Email
> 
> On Fri, Aug 16, 2019 at 4:14 AM Wen He <wen.he_1@nxp.com> wrote:
> >
> > Add optional property node 'arm,malidp-arqos-value' for the Mali DP500.
> > This property describe the ARQoS levels of DP500's QoS signaling.
> >
> > Signed-off-by: Wen He <wen.he_1@nxp.com>
> > ---
> > change in v3:
> >         - correction the describe of the node
> >
> >  Documentation/devicetree/bindings/display/arm,malidp.txt | 3 +++
> >  1 file changed, 3 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/display/arm,malidp.txt
> b/Documentation/devicetree/bindings/display/arm,malidp.txt
> > index 2f7870983ef1..1f711d32f235 100644
> > --- a/Documentation/devicetree/bindings/display/arm,malidp.txt
> > +++ b/Documentation/devicetree/bindings/display/arm,malidp.txt
> > @@ -37,6 +37,8 @@ Optional properties:
> >
> Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt)
> >      to be used for the framebuffer; if not present, the framebuffer may
> >      be located anywhere in memory.
> > +  - arm,malidp-arqos-high-level: phandle to describing the ARQoS levels of
> DP500's
> > +    QoS signaling.
> 
> The driver is reading a u32... Did you test this?

Sure, actually, here should be use a u32 value....

The older description was correct, sorry, I should be
Correction the example node define...

'integer of u32 value describing the ARQoS levels of DP500's QoS signaling', 

> 
> 
> >
> >
> >  Example:
> > @@ -54,6 +56,7 @@ Example:
> >                 clocks = <&oscclk2>, <&fpgaosc0>, <&fpgaosc1>,
> <&fpgaosc1>;
> >                 clock-names = "pxlclk", "mclk", "aclk", "pclk";
> >                 arm,malidp-output-port-lines = /bits/ 8 <8 8 8>;
> > +               arm,malidp-arqos-high-level = <&rqosvalue>;
					arm,malidp-arqos-high-level = < 0xd000d000>;

Best Regards,
Wen

> >                 port {
> >                         dp0_output: endpoint {
> >                                 remote-endpoint =
> <&tda998x_2_input>;
> > --
> > 2.17.1
> >

      reply	other threads:[~2019-08-19  2:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 10:04 [v3 1/2] dt/bindings: display: Add optional property node for Mali DP500 Wen He
2019-08-16 10:04 ` [v3 2/2] drm/arm/mali-dp: Add display QoS interface configuration " Wen He
2019-08-16 20:09 ` [v3 1/2] dt/bindings: display: Add optional property node " Rob Herring
2019-08-19  2:13   ` Wen He [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=DB7PR04MB5195A94A64615FF44C0F4442E2A80@DB7PR04MB5195.eurprd04.prod.outlook.com \
    --to=wen.he_1@nxp.com \
    --cc=airlied@linux.ie \
    --cc=brian.starkey@arm.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-devel@linux.nxdi.nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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 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.