From: Archit Taneja <archit@ti.com>
To: hvaibhav@ti.com
Cc: tomi.valkeinen@ti.com, linux-omap@vger.kernel.org,
sumit.semwal@ti.com, linux-media@vger.kernel.org,
Archit Taneja <archit@ti.com>
Subject: [PATCH v3 0/4] OMAP_VOUT: Misc fixes and cleanup patches for 3.2
Date: Mon, 26 Sep 2011 17:29:21 +0530 [thread overview]
Message-ID: <1317038365-30650-1-git-send-email-archit@ti.com> (raw)
This set includes patches which do the following:
- Fix crash if a we call dssdev->driver->update for a disabled panel.
- Fix the issue of not being able to request for a buffer which is larger than
what we did the last time.
- Remove some redundant code in omap_vout_isr()
- Add basic support for DSI panels
Changes in v3:
- Remove patch "OMAP_VOUT: Fix VSYNC IRQ handling in omap_vout_isr" since its
still not clear whether its needed or not.
Refernce base:
git@gitorious.org:~boddob/linux-omap-dss2/archit-dss2-clone.git 'for_omap_vout2'
Archit Taneja (4):
OMAP_VOUT: Fix check in reqbuf for buf_size allocation
OMAP_VOUT: CLEANUP: Remove redundant code from omap_vout_isr
OMAP_VOUT: Add support for DSI panels
OMAP_VOUT: Don't trigger updates in omap_vout_probe
drivers/media/video/omap/omap_vout.c | 191 ++++++++++++++++------------------
1 files changed, 91 insertions(+), 100 deletions(-)
next reply other threads:[~2011-09-26 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 11:59 Archit Taneja [this message]
2011-09-26 11:59 ` [PATCH v3 1/4] OMAP_VOUT: Fix check in reqbuf for buf_size allocation Archit Taneja
2011-09-27 7:19 ` Hiremath, Vaibhav
2011-09-27 7:23 ` Archit Taneja
2011-09-26 11:59 ` [PATCH v3 2/4] OMAP_VOUT: CLEANUP: Remove redundant code from omap_vout_isr Archit Taneja
2011-09-26 11:59 ` [PATCH v3 3/4] OMAP_VOUT: Add support for DSI panels Archit Taneja
2011-09-26 11:59 ` [PATCH v3 4/4] OMAP_VOUT: Don't trigger updates in omap_vout_probe Archit Taneja
2011-09-27 6:10 ` Tomi Valkeinen
2011-09-27 7:02 ` Archit Taneja
2011-09-27 7:07 ` Tomi Valkeinen
2011-09-27 7:15 ` Archit Taneja
2011-09-27 6:26 ` Hiremath, Vaibhav
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=1317038365-30650-1-git-send-email-archit@ti.com \
--to=archit@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sumit.semwal@ti.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