From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: tomi.valkeinen@ti.com, laurent.pinchart@ideasonboard.com
Cc: airlied@linux.ie, devicetree@vger.kernel.org, jsarha@ti.com,
dri-devel@lists.freedesktop.org
Subject: [PATCH v3 0/3] drm/omap: Support for dispc memory bandwidth limit
Date: Thu, 30 Nov 2017 14:12:34 +0200 [thread overview]
Message-ID: <20171130121237.30431-1-peter.ujfalusi@ti.com> (raw)
Hi,
Changes since v2:
- Rebased on drm-next (v2 was based on drm-next and my
'drm/omap: Module parameter for display order configuration' series, thus it
was not applying cleanly.
- Added Acked-by from Rob to the dt-binding changes
Changes since v1:
- Use the crtc->mode_valid and not connector->mode_valid as the limit is really
posed by the 'crtc' (DISPC)
- Bandwidth calculation changed: do the calculation in place + extended comment
- looked for better place to document the max-memory-bandwidth, but
can not find any suitable document. Creating a new txt file for only one
property did not seemed feasable.
This series will add simple memory bandwidth limit support to reject modes
which, if used with one plane in full size would fail the limit.
Regards,
Peter
---
Peter Ujfalusi (3):
dt-bindings: display/ti: Add optional property to set memory bandwidth
limit
drm/omap: dss: Add support for reporting memory bandwidth limitation
drm/omap: Filter displays mode based on bandwidth limit
.../devicetree/bindings/display/ti/ti,dra7-dss.txt | 5 +++
.../bindings/display/ti/ti,omap2-dss.txt | 4 +++
.../bindings/display/ti/ti,omap3-dss.txt | 4 +++
.../bindings/display/ti/ti,omap4-dss.txt | 4 +++
.../bindings/display/ti/ti,omap5-dss.txt | 4 +++
drivers/gpu/drm/omapdrm/dss/dispc.c | 13 ++++++++
drivers/gpu/drm/omapdrm/dss/omapdss.h | 2 ++
drivers/gpu/drm/omapdrm/omap_crtc.c | 37 ++++++++++++++++++++++
drivers/gpu/drm/omapdrm/omap_drv.c | 5 +++
drivers/gpu/drm/omapdrm/omap_drv.h | 3 ++
10 files changed, 81 insertions(+)
--
Peter
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
next reply other threads:[~2017-11-30 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 12:12 Peter Ujfalusi [this message]
2017-11-30 12:12 ` [PATCH v3 1/3] dt-bindings: display/ti: Add optional property to set memory bandwidth limit Peter Ujfalusi
[not found] ` <20171130121237.30431-1-peter.ujfalusi-l0cyMroinI0@public.gmane.org>
2017-11-30 12:12 ` [PATCH v3 2/3] drm/omap: dss: Add support for reporting memory bandwidth limitation Peter Ujfalusi
2017-11-30 12:12 ` [PATCH v3 3/3] drm/omap: Filter displays mode based on bandwidth limit Peter Ujfalusi
2017-12-01 11:54 ` [PATCH v3 0/3] drm/omap: Support for dispc memory " Tomi Valkeinen
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=20171130121237.30431-1-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--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