Devicetree
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, tomi.valkeinen@ti.com,
	laurent.pinchart@ideasonboard.com,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] dt-bindings: display/ti: Add optional property to set memory bandwidth limit
Date: Mon, 30 Oct 2017 15:53:52 +0200	[thread overview]
Message-ID: <1435c3bd-627d-3382-447e-af39fdd137ab@ti.com> (raw)
In-Reply-To: <20171027022711.624bnvldhfdq4rew@rob-hp-laptop>

Rob,

On 10/27/2017 05:27 AM, Rob Herring wrote:
> On Fri, Oct 20, 2017 at 04:12:56PM +0300, Peter Ujfalusi wrote:
>> max-memory-bandwidth can be used to specify the maximum bandwidth dispc
>> can use when reading display data from main memory.
>>
>> In some SoC (am437x for example) we have memory bandwidth limitation
>> which causes underflow in the display subsystem.
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>> ---
>>  Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt  | 5 +++++
>>  Documentation/devicetree/bindings/display/ti/ti,omap2-dss.txt | 4 ++++
>>  Documentation/devicetree/bindings/display/ti/ti,omap3-dss.txt | 4 ++++
>>  Documentation/devicetree/bindings/display/ti/ti,omap4-dss.txt | 4 ++++
>>  Documentation/devicetree/bindings/display/ti/ti,omap5-dss.txt | 4 ++++
>>  5 files changed, 21 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt b/Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt
>> index c30f9ec189ed..91279f1060fe 100644
>> --- a/Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt
>> +++ b/Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt
>> @@ -47,6 +47,11 @@ Required properties:
>>  - clocks: handle to fclk
>>  - clock-names: "fck"
>>  
>> +Optional properties:
>> +- max-memory-bandwidth: Input memory (from main memory to dispc) bandwidth limit
>> +			in bytes per second
> 
> Can we move this to a common location since we already have the same 
> prop for ARM pl11x.

This is why I used the same string for ti,* as I saw that pl11x have it
documented (the driver is not supporting it afaik, it is in the TODO).

I don't see any generic documentation for Display, not sure what would be the
best place for things like this.

While it is true that memory bandwidth limit can be a generic property, but it
might (not sure about it) can apply to different interfaces among different
vendors. The device specific documentation should either way need to mention
that it supports memory bandwidth limitation or not.

-- 
Péter

Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-10-30 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 13:12 [PATCH 0/3] drm/omap: Support for dispc memory bandwidth limit Peter Ujfalusi
2017-10-20 13:12 ` [PATCH 1/3] dt-bindings: display/ti: Add optional property to set " Peter Ujfalusi
     [not found]   ` <20171020131258.4092-2-peter.ujfalusi-l0cyMroinI0@public.gmane.org>
2017-10-27  2:27     ` Rob Herring
2017-10-30 13:53       ` Peter Ujfalusi [this message]
     [not found] ` <20171020131258.4092-1-peter.ujfalusi-l0cyMroinI0@public.gmane.org>
2017-10-20 13:12   ` [PATCH 2/3] drm/omap: dss: Add support for reporting memory bandwidth limitation Peter Ujfalusi
2017-10-20 13:12 ` [PATCH 3/3] drm/omap: Filter displays mode based on bandwidth limit Peter Ujfalusi
2017-10-20 13:34   ` Daniel Vetter

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=1435c3bd-627d-3382-447e-af39fdd137ab@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=robh@kernel.org \
    --cc=tomi.valkeinen@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox