From: Guruswamy Senthilvadivu <svadivu@ti.com>
To: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
tony@atomide.com, tomi.valkeinen@nokia.com, hvaibhav@ti.com
Cc: Senthilvadivu Guruswamy <svadivu@ti.com>
Subject: [PATCH v4 3/3] OMAP: DSS2: OMAPFB: Allow usage of def_vrfb only for omap2,3
Date: Tue, 22 Jun 2010 11:57:22 +0000 [thread overview]
Message-ID: <1277207827-15833-4-git-send-email-svadivu@ti.com> (raw)
In-Reply-To: <1277207827-15833-3-git-send-email-svadivu@ti.com>
From: Senthilvadivu Guruswamy <svadivu@ti.com>
Force def_vrfb to 0 for non omap2, omap3 devices
Signed-off-by: Senthilvadivu Guruswamy <svadivu@ti.com>
---
drivers/video/omap2/omapfb/omapfb-main.c | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/drivers/video/omap2/omapfb/omapfb-main.c b/drivers/video/omap2/omapfb/omapfb-main.c
index 4b4506d..0f79db8 100644
--- a/drivers/video/omap2/omapfb/omapfb-main.c
+++ b/drivers/video/omap2/omapfb/omapfb-main.c
@@ -2128,6 +2128,16 @@ static int omapfb_probe(struct platform_device *pdev)
goto err0;
}
+ /* TODO : Replace cpu check with omap_has_vrfb once HAS_FEATURE
+ * available for OMAP2 and OMAP3
+ */
+ if (def_vrfb && (!cpu_is_omap24xx()) && (!cpu_is_omap34xx())) {
+ def_vrfb = 0;
+ dev_warn(&pdev->dev, "VRFB is not in this device,"
+ "using DMA for rotation\n");
+ }
+
+
mutex_init(&fbdev->mtx);
fbdev->dev = &pdev->dev;
--
1.6.3.3
prev parent reply other threads:[~2010-06-22 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 11:57 [PATCH v4 0/3] OMAP: DSS2: OMAPFB: Allow FB_OMAP2 to build without VRFB Guruswamy Senthilvadivu
2010-06-22 11:57 ` [PATCH v4 1/3] " Guruswamy Senthilvadivu
2010-06-22 11:57 ` [PATCH v4 2/3] OMAP: DSS2: OMAPFB: make VRFB depends on OMAP2,3 Guruswamy Senthilvadivu
2010-06-22 11:57 ` Guruswamy Senthilvadivu [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=1277207827-15833-4-git-send-email-svadivu@ti.com \
--to=svadivu@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).