From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: linux-fbdev@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 0/7] OMAPDSS: Support multiple DPI instances
Date: Thu, 26 Jun 2014 12:28:50 +0000 [thread overview]
Message-ID: <53AC1202.5050901@ti.com> (raw)
In-Reply-To: <1401864063-19196-1-git-send-email-archit@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
On 04/06/14 09:40, Archit Taneja wrote:
> DSS on DRA7x has 3 DPI outputs. In order to get them to work. We need to make
> the DPI driver support multiple DPI instances. We also need to tweak the
> DT parsing done to match an encoder/connector/panel driver to find the
> corresponding omapdss output. This series tries to achieve the above 2 tasks.
>
> Changes in v3:
>
> - Make indexes in port lists not depend on DPI and SDI CONFIGs.
> - Cleaner code in dss_init_ports/uninit_ports.
> - Split up the patch which creates multi DPI instances.
> - Switch to a simpler way of extracting DPI driver data from dssdev.
> - Change some of the dss-of fucntions, such that
> omapdss_of_find_source_for_first_ep is simplified.
>
> Archit Taneja (7):
> OMAPDSS: DPI: Use DPI driver data
> OMAPDSS: DPI: Allocate driver data
> OMAPDSS: DPI: Store dpi_data pointer in the DT port's data
> OMAPDSS: DSS: init dss ports cleanly
> OMAPDSS: DT: Get source endpoint by matching reg-id
> OMAPDSS: DPI: Add support for multiple instances
> omapdss: DSS: add reg-id param to dpi_select_source
>
> .../fbdev/omap2/displays-new/encoder-tfp410.c | 1 +
> .../fbdev/omap2/displays-new/encoder-tpd12s015.c | 1 +
> drivers/video/fbdev/omap2/dss/dpi.c | 259 ++++++++++++++-------
> drivers/video/fbdev/omap2/dss/dss-of.c | 58 +++--
> drivers/video/fbdev/omap2/dss/dss.c | 108 +++++++--
> drivers/video/fbdev/omap2/dss/dss.h | 34 ++-
> drivers/video/fbdev/omap2/dss/output.c | 19 +-
> drivers/video/fbdev/omap2/dss/sdi.c | 2 +-
> include/video/omapdss.h | 5 +-
> 9 files changed, 354 insertions(+), 133 deletions(-)
Other than the couple minor comments I had, the series looks good.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-06-26 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1401096492-1405-1-git-send-email-archit@ti.com>
2014-06-04 6:52 ` [PATCH v3 0/7] OMAPDSS: Support multiple DPI instances Archit Taneja
2014-06-04 6:52 ` [PATCH v3 1/7] OMAPDSS: DPI: Use DPI driver data Archit Taneja
2014-06-04 6:52 ` [PATCH v3 2/7] OMAPDSS: DPI: Allocate " Archit Taneja
2014-06-04 6:52 ` [PATCH v3 3/7] OMAPDSS: DPI: Store dpi_data pointer in the DT port's data Archit Taneja
2014-06-04 6:53 ` [PATCH v3 4/7] OMAPDSS: DSS: init dss ports cleanly Archit Taneja
2014-06-26 12:16 ` Tomi Valkeinen
2014-06-04 6:53 ` [PATCH v3 5/7] OMAPDSS: DT: Get source endpoint by matching reg-id Archit Taneja
2014-06-04 6:53 ` [PATCH v3 6/7] OMAPDSS: DPI: Add support for multiple instances Archit Taneja
2014-06-26 12:15 ` Tomi Valkeinen
2014-06-04 6:53 ` [PATCH v3 7/7] omapdss: DSS: add reg-id param to dpi_select_source Archit Taneja
2014-06-26 12:28 ` Tomi Valkeinen [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=53AC1202.5050901@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).