From: Felipe Balbi <me@felipebalbi.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <felipe.balbi@nokia.com>,
"Tereshonkov Roman (Nokia-D/Helsinki)"
<roman.tereshonkov@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
juha.yrjola@solidboot.com
Subject: Re: [PATCH] OMAP3: SDTI: Prevent access to sdti writing if module is not initialized.
Date: Fri, 27 Feb 2009 21:00:53 +0200 [thread overview]
Message-ID: <20090227190053.GH16801@frodo> (raw)
In-Reply-To: <20090227183524.GI11594@atomide.com>
On Fri, Feb 27, 2009 at 10:35:25AM -0800, Tony Lindgren wrote:
> * Felipe Balbi <felipe.balbi@nokia.com> [090216 03:50]:
> > On Thu, Feb 12, 2009 at 12:39:28PM +0100, Tereshonkov Roman wrote:
> > > The function sti_channel_write_trace can be run from process and interrupt
> > > context. It has to be completed before other sti_channel_write_trace calls.
> > >
> > > Prevent sdti writing when SDTI module is not initialized.
>
> Roman, can you please create a patch against the mainline tree and send
> this driver to LKML for integration? I think pretty much the only thing
> you should do is get rid of the OMAP_TAG_STI_CONSOLE and use get that
> option from kernel command line like all the other consoles do.
Adding Juha to Cc as he had some comments about the OMAP_TAG_STI_CONSOLE
regarding our products.
Juha could you comment again what were the problems on starting the sti
console based on console= command line ??
--
balbi
next prev parent reply other threads:[~2009-02-27 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 11:39 [PATCH] OMAP3: SDTI: Prevent access to sdti writing if module is not initialized Roman Tereshonkov
2009-02-16 11:33 ` Felipe Balbi
2009-02-27 18:35 ` Tony Lindgren
2009-02-27 19:00 ` Felipe Balbi [this message]
2009-02-28 10:08 ` Juha Yrjola
2009-03-02 8:27 ` Lauri Leukkunen
2009-03-02 11:31 ` Juha Yrjola
2009-03-02 12:15 ` Lauri Leukkunen
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=20090227190053.GH16801@frodo \
--to=me@felipebalbi.com \
--cc=felipe.balbi@nokia.com \
--cc=juha.yrjola@solidboot.com \
--cc=linux-omap@vger.kernel.org \
--cc=roman.tereshonkov@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