From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Archit Taneja <archit@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/4] OMAP: DSS2: Miscellaneous DSI cleanup and fixes
Date: Tue, 17 May 2011 14:58:39 +0300 [thread overview]
Message-ID: <1305633519.1847.12.camel@deskari> (raw)
In-Reply-To: <1305539229-28560-1-git-send-email-archit@ti.com>
On Mon, 2011-05-16 at 15:17 +0530, Archit Taneja wrote:
> Some minor fixes/cleanup for DSI:
> - Remove some debug prints in dsi_dump_clocks().
> - Use system workqueue instead of creating a private one.
> - Add num_data_lanes and line_buffer_size and get the from DSI_GNQ register.
>
> Archit Taneja (4):
> OMAP: DSS2: DSI: Remove DISPC pixel clock related info in
> dsi_dump_clocks()
> OMAP: DSS2: DSI: Use system workqueue for delayed work instead of a
> private workqueue
> OMAP: DSS2: DSI: Get number of DSI data lanes using DSI_GNQ register
> OMAP: DSS2: DSI: Get line buffer size from DSI_GNQ register
>
> drivers/video/omap2/dss/dsi.c | 163 +++++++++++++++++++++++++-------
> drivers/video/omap2/dss/dss_features.c | 3 +-
> drivers/video/omap2/dss/dss_features.h | 1 +
> include/video/omapdss.h | 4 +
> 4 files changed, 134 insertions(+), 37 deletions(-)
Thanks, applied.
Tomi
prev parent reply other threads:[~2011-05-17 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 9:47 [PATCH 0/4] OMAP: DSS2: Miscellaneous DSI cleanup and fixes Archit Taneja
2011-05-16 9:47 ` [PATCH 1/4] OMAP: DSS2: DSI: Remove DISPC pixel clock related info in dsi_dump_clocks() Archit Taneja
2011-05-16 9:47 ` [PATCH 2/4] OMAP: DSS2: DSI: Use system workqueue for delayed work instead of a private workqueue Archit Taneja
2011-05-16 9:47 ` [PATCH 3/4] OMAP: DSS2: DSI: Get number of DSI data lanes using DSI_GNQ register Archit Taneja
2011-05-16 9:47 ` [PATCH 4/4] OMAP: DSS2: DSI: Get line buffer size from " Archit Taneja
2011-05-17 11:58 ` 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=1305633519.1847.12.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--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