From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: "ext Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
"Deak Imre (Nokia-D/Helsinki)" <imre.deak@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC][PATCH] omapfb: Condition mutex acquisition
Date: Wed, 30 Sep 2009 11:35:32 +0300 [thread overview]
Message-ID: <1254299732.23991.57.camel@tubuntu> (raw)
In-Reply-To: <20090930005310.GI16865@atomide.com>
On Wed, 2009-09-30 at 02:53 +0200, ext Tony Lindgren wrote:
> * Tomi Valkeinen <tomi.valkeinen@nokia.com> [090929 07:54]:
> > On Tue, 2009-09-29 at 16:34 +0200, ext Aguirre Rodriguez, Sergio Alberto
> > wrote:
> > > From: Tomi Valkeinen [tomi.valkeinen@nokia.com]
> > > Sent: Tuesday, September 29, 2009 9:22 AM
> > > > On Tue, 2009-09-29 at 16:14 +0200, ext Aguirre Rodriguez, Sergio Alberto
> > > > wrote:
> > > > > From: Sergio Aguirre <saaguirre@ti.com>
> > > > >
> > > > > Acquiring mutex before framebuffer registration doesn't make sense,
> > > > > As there's no danger of external access to the memory related fields.
> > > >
> > > > What problem does this patch solve? It makes the code more complex.
> > > >
> > >
> > > Tomi,
> > >
> > > Thanks for your time.
> > >
> > > The problem was that, during platform driver registration,
> > > this sequence was executed:
> > >
> > > -> omapfb_probe
> > > -> omapfb_do_probe
> > > -> planes_init
> > > -> fbinfo_init
> > > -> set_fb_fix
> > > ...
> > > -> register_framebuffer
> > >
> > > And then, inside that function, an attempt of acquiring a
> > > mutex failed, because it wasn't initialized before trying it:
> > >
> > > mutex_lock(&fbi->mm_lock);
> > >
> > > It is actually initialized later in omapfb_do_probe in register_framebuffer call.
> > >
> > > So, how is the best to solve this then?
> >
> > Oh, I wasn't implying that there's something wrong with the fix, I just
> > didn't know what it was fixing =).
> >
> > Looks like a valid fix to me.
>
> Tomi & Imre, do you want me to add this to the omap-fixes queue,
> or are you planning to send other fixes too?
>
> If you want me to add it, please reply with your ack.
>
> I'll added it into omap-fixes-testing branch for now so we can
> get the omaps booted.
I don't know if Imre wants to handle this (probably not =), but I would
rather concentrate on DSS2 patches. I have enough of them already, and
my progress in upstreaming them seems to be... slow... =).
So if you can take any minor old-omapfb patches to omap-fixes queue,
it'd be great.
Acked-by: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Tomi
next prev parent reply other threads:[~2009-09-30 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 14:14 [RFC][PATCH] omapfb: Condition mutex acquisition Aguirre Rodriguez, Sergio Alberto
2009-09-29 14:22 ` Tomi Valkeinen
2009-09-29 14:34 ` Aguirre Rodriguez, Sergio Alberto
2009-09-29 14:37 ` Aguirre Rodriguez, Sergio Alberto
2009-09-29 14:43 ` Hunter, Jon
2009-09-29 14:53 ` Tomi Valkeinen
2009-09-29 14:56 ` Aguirre Rodriguez, Sergio Alberto
2009-09-29 18:26 ` Hiremath, Vaibhav
2009-09-30 8:32 ` Tomi Valkeinen
2009-09-30 0:53 ` Tony Lindgren
2009-09-30 8:35 ` Tomi Valkeinen [this message]
2009-09-30 12:08 ` Imre Deak
2009-09-30 13:34 ` Aguirre Rodriguez, Sergio Alberto
2009-09-30 15:34 ` Tony Lindgren
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=1254299732.23991.57.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=imre.deak@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.