2019-08-16 10:17:08

by Wen He

[permalink] [raw]
Subject: [v3 1/2] dt/bindings: display: Add optional property node for Mali DP500

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 <[email protected]>
---
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.


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>;
port {
dp0_output: endpoint {
remote-endpoint = <&tda998x_2_input>;
--
2.17.1


2019-08-16 20:10:29

by Rob Herring

[permalink] [raw]
Subject: Re: [v3 1/2] dt/bindings: display: Add optional property node for Mali DP500

On Fri, Aug 16, 2019 at 4:14 AM Wen He <[email protected]> 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 <[email protected]>
> ---
> 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?


>
>
> 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>;
> port {
> dp0_output: endpoint {
> remote-endpoint = <&tda998x_2_input>;
> --
> 2.17.1
>

2019-08-19 02:14:53

by Wen He

[permalink] [raw]
Subject: RE: [EXT] Re: [v3 1/2] dt/bindings: display: Add optional property node for Mali DP500



> -----Original Message-----
> From: Rob Herring <[email protected]>
> Sent: 2019年8月17日 4:09
> To: Wen He <[email protected]>
> Cc: [email protected]; Liviu Dudau <[email protected]>;
> Brian Starkey <[email protected]>; David Airlie <[email protected]>; Daniel
> Vetter <[email protected]>; Mark Rutland <[email protected]>; dri-devel
> <[email protected]>; [email protected];
> [email protected]; Leo Li <[email protected]>
> 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 <[email protected]> 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 <[email protected]>
> > ---
> > 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
> >