From: Peter Barada <peterb@logicpd.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
"linux-fbdev-devel@lists.sourceforge.net"
<linux-fbdev-devel@lists.sourceforge.net>,
Imre Deak <imre.deak@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [RFC][PATCH] omapfb: Reorder Register_framebuffer call
Date: Fri, 04 Sep 2009 09:34:28 -0400 [thread overview]
Message-ID: <1252071268.2507.1.camel@blitz> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB030A0071B9@dbde02.ent.ti.com>
On Fri, 2009-09-04 at 12:14 +0530, Gadiyar, Anand wrote:
> > From: Sergio Aguirre <saaguirre@ti.com>
> >
> > This fixes the issue in which mm_lock mutex was attempted to be
> > used without initializing previously.
> >
> > Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
>
> Tested-by: Anand Gadiyar <gadiyar@ti.com>
>
> This patch on top of current linux-omap kernel allows me to
> boot with the default SDP defconfig on a 3430 SDP.
Tested-by: Peter Barada <peterb@logicpd.com>
This patch on top of current linux-omap kernel allows me to boot with
the LCD enabled on LogicPD's OMAP boards.
> > ---
> > drivers/video/omap/omapfb_main.c | 20 +++++++++++---------
> > 1 files changed, 11 insertions(+), 9 deletions(-)
> >
> > diff --git a/drivers/video/omap/omapfb_main.c b/drivers/video/omap/omapfb_main.c
> > index 125e605..60f9482 100644
> > --- a/drivers/video/omap/omapfb_main.c
> > +++ b/drivers/video/omap/omapfb_main.c
> > @@ -1503,12 +1503,21 @@ static int fbinfo_init(struct omapfb_device *fbdev, struct fb_info *info)
> > var->rotate = def_rotate;
> > var->bits_per_pixel = fbdev->panel->bpp;
> >
> > + r = register_framebuffer(info);
> > + if (r != 0) {
> > + dev_err(fbdev->dev,
> > + "registering framebuffer failed\n");
> > + return r;
> > + }
> > +
> > set_fb_var(info, var);
> > set_fb_fix(info);
> >
> > r = fb_alloc_cmap(&info->cmap, 16, 0);
> > - if (r != 0)
> > + if (r != 0) {
> > dev_err(fbdev->dev, "unable to allocate color map memory\n");
> > + unregister_framebuffer(info);
> > + }
> >
> > return r;
> > }
> > @@ -1773,15 +1782,8 @@ static int omapfb_do_probe(struct platform_device *pdev,
> > init_state++;
> >
> > vram = 0;
> > - for (i = 0; i < fbdev->mem_desc.region_cnt; i++) {
> > - r = register_framebuffer(fbdev->fb_info[i]);
> > - if (r != 0) {
> > - dev_err(fbdev->dev,
> > - "registering framebuffer %d failed\n", i);
> > - goto cleanup;
> > - }
> > + for (i = 0; i < fbdev->mem_desc.region_cnt; i++)
> > vram += fbdev->mem_desc.region[i].size;
> > - }
> >
> > fbdev->state = OMAPFB_ACTIVE;
> >
> > --
> > 1.6.3.2
> >
> > --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Peter Barada <peterb@logicpd.com>
Logic Product Development, Inc.
next prev parent reply other threads:[~2009-09-04 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 20:12 [RFC][PATCH] omapfb: Reorder Register_framebuffer call Aguirre Rodriguez, Sergio Alberto
2009-09-04 6:44 ` Gadiyar, Anand
2009-09-04 8:33 ` Hiremath, Vaibhav
2009-09-04 13:34 ` Peter Barada [this message]
2009-09-05 1:41 ` Eric Witcher
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=1252071268.2507.1.camel@blitz \
--to=peterb@logicpd.com \
--cc=gadiyar@ti.com \
--cc=imre.deak@nokia.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@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;
as well as URLs for NNTP newsgroup(s).