From: Andrzej Hajda <a.hajda@samsung.com>
To: Ajay Kumar <ajaykumar.rs@samsung.com>,
dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org
Cc: seanpaul@google.com, sw0312.kim@samsung.com, joshi@samsung.com,
ajaynumb@gmail.com, marcheu@chromium.org,
prashanth.g@samsung.com
Subject: Re: [RFC 0/4] drm: exynos: Add drivers for MDNIE and IELCD
Date: Tue, 01 Apr 2014 11:23:49 +0200 [thread overview]
Message-ID: <533A85A5.4000605@samsung.com> (raw)
In-Reply-To: <1395238975-24600-1-git-send-email-ajaykumar.rs@samsung.com>
Hi Ajay,
Thanks for the patchset.
On 03/19/2014 03:22 PM, Ajay Kumar wrote:
> This series is based on exynos-drm-next-todo branch of Inki Dae's tree at:
> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git
>
> On Exynos SOC, FIMD supports various post processors
> like MIE, MDNIE and IELCD for image enhancement purposes.
> This patchset adds an infrastructure in exynos FIMD to support such
> post procerssors and also adds support routines for MDNIE, and IELCD.
I
>
> (1) For basic display output,
> -- MDNIE and IELCD should have same video timings as FIMD (mode_set)
> -- strict power_up/down sequence need to be followed between FIMD,
> MDNIE, and IELCD (power_on, power_off)
>
> (2) For enhanced display output,
> -- MDNIE needs image enhancement data from userspace
> (set_property and set_gamma)
>
> Rahul Sharma's patchset at:
> http://comments.gmane.org/gmane.linux.kernel.samsung-soc/27642
> The above patchset is needed to support the enhanced display output.
There should be also patches adding enhanced output support for
exynos_drm framework, I have not found any on dri-devel list.
>
> MDNIE and IELCD DT nodes are given as phandles to FIMD DT node.
I wonder if it wouldn't be better to use video interface links here,
instead of creating new properties and describing dependency between
them we would just use standard(almost :) ) video links to connect nodes:
FIMD ---> mDNIe ---> IELCD ---> ...
FIMD ---> MIE ---> ...
...
> SOC specific information like base address, clocks and other
> configuration information are extracted via FIMD DT node.
All bindings should be documented in separate patches with device-tree
maintainers added to CC.
It would be nice to have information on which boards it has been tested.
Patches to DTS files of existing boards will be also helpful.
Regards
Andrzej
>
> Ajay Kumar, Shirish, Rahul Sharma (4):
> drm: exynos: Add infrastructure to support FIMD post processors
> drm: exynos: add MDNIE post processor
> drm: exynos: add IELCD post processor
> drm: exynos: add MDNIE and IELCD to FIMD pp list
>
> drivers/gpu/drm/exynos/Makefile | 3 +-
> drivers/gpu/drm/exynos/exynos_drm_fimd.c | 179 ++++++++
> drivers/gpu/drm/exynos/exynos_fimd_pp.h | 54 +++
> drivers/gpu/drm/exynos/exynos_ielcd.c | 295 ++++++++++++
> drivers/gpu/drm/exynos/exynos_mdnie.c | 707 +++++++++++++++++++++++++++++
> drivers/gpu/drm/exynos/exynos_mdnie_regs.h | 154 +++++++
> include/video/samsung_fimd.h | 49 +-
> 7 files changed, 1439 insertions(+), 2 deletions(-)
> create mode 100644 drivers/gpu/drm/exynos/exynos_fimd_pp.h
> create mode 100644 drivers/gpu/drm/exynos/exynos_ielcd.c
> create mode 100644 drivers/gpu/drm/exynos/exynos_mdnie.c
> create mode 100644 drivers/gpu/drm/exynos/exynos_mdnie_regs.h
>
prev parent reply other threads:[~2014-04-01 9:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 14:22 [RFC 0/4] drm: exynos: Add drivers for MDNIE and IELCD Ajay Kumar
2014-03-19 14:22 ` [RFC 1/4] drm: exynos: Add infrastructure to support FIMD post processors Ajay Kumar
2014-03-31 12:04 ` Andrzej Hajda
2014-03-19 14:22 ` [RFC 2/4] drm: exynos: add MDNIE post processor Ajay Kumar
2014-03-19 17:21 ` Sachin Kamat
2014-03-21 14:30 ` Ajay kumar
2014-04-01 8:01 ` Andrzej Hajda
2014-03-19 14:22 ` [RFC 3/4] drm: exynos: add IELCD " Ajay Kumar
2014-03-21 8:42 ` Sachin Kamat
2014-03-21 15:44 ` Ajay kumar
2014-04-01 8:54 ` Andrzej Hajda
2014-03-19 14:22 ` [RFC 4/4] drm: exynos: add MDNIE and IELCD to FIMD pp list Ajay Kumar
2014-04-01 9:06 ` Andrzej Hajda
2014-04-01 9:23 ` Andrzej Hajda [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=533A85A5.4000605@samsung.com \
--to=a.hajda@samsung.com \
--cc=ajaykumar.rs@samsung.com \
--cc=ajaynumb@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=joshi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=prashanth.g@samsung.com \
--cc=seanpaul@google.com \
--cc=sw0312.kim@samsung.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.