public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: Kevin Hilman <khilman@mvista.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: OMAP1 realtime patch
Date: Thu, 08 Feb 2007 16:01:59 +0100	[thread overview]
Message-ID: <45CB3B67.3090907@googlemail.com> (raw)
In-Reply-To: <1170882015.11368.25.camel@vence.hilman.org>

Kevin Hilman wrote:
> On Mon, 2007-02-05 at 20:29 +0100, Dirk Behme wrote:
> 
>>For everybody interested please find in attachment my OMAP1
>>realtime patch.
>  
> Was there a reason for the raw_spinlock conversions? 

Not really ;)

> Did you run into
> specific issues for converting those?  

There was this ethernet/irq/gpio issue we fixed with 
workaround in kernel/irq/manage.c. Until we had this the 
root cause was unclear so a lot of raw_spinlock to be on the 
safe side for debugging. Then, I posted my patch to have a 
starting point people can try and improve, as you did :)

> Here is a patch which leaves out the raw_spinlock conversions.  It goes
> on the OMAP git tree on top of -rt5 (ignoring conflicts.)  I've left out
> all the raw_spinlock conversions.  This has been tested on an
> OMAP1623/H2 platform.

Many thanks for the update!

> Index: dev/kernel/printk.c
> ===================================================================
> --- dev.orig/kernel/printk.c
> +++ dev/kernel/printk.c
> @@ -464,6 +464,7 @@ static void zap_locks(void)
>  	spin_lock_init(&logbuf_lock);
>  	/* And make sure that we print immediately */
>  	init_MUTEX(&console_sem);
> +	zap_rt_locks();
>  }

What's this?

Btw: You removed the HRTIMER_MODE_REL and enum 
hrtimer_restart changes in 
drivers/input/touchscreen/ads7846.c as well?

Cheers

Dirk

  reply	other threads:[~2007-02-08 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-05 19:29 OMAP1 realtime patch Dirk Behme
2007-02-07 21:00 ` Kevin Hilman
2007-02-08 15:01   ` Dirk Behme [this message]
2007-02-08 18:09   ` Dirk Behme
2007-02-11 17:01     ` Dirk Behme
2007-02-12 19:24       ` Kevin Hilman
2007-02-12 19:32         ` Kevin Hilman
2007-02-12 20:34         ` Dirk Behme

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=45CB3B67.3090907@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=khilman@mvista.com \
    --cc=linux-omap-open-source@linux.omap.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