public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: Recent git kernels and OSK
Date: Fri, 06 Oct 2006 11:58:18 +0200	[thread overview]
Message-ID: <452628BA.4000907@gmail.com> (raw)
In-Reply-To: <452378FA.9050604@gmail.com>

Dirk Behme wrote:
> Doing some more debugging (with low level debug disabled now) shows that 
> at least until "ARM: OMAP: DSPGW: mailbox log cleanup" [1] everything is 
> okay. Then, with all changes including "ARM: OMAP: DSPGW: Peripheral 
> (kfunc) control" [2] it seems to be broken.

After some additional hours of debugging it's a really
simple bug: A strcmp() mismatch which results in
omap_dsp->mbox being a NULL pointer.

In mach-omap1/mailbox.c the mailbox name is .name = "DSP"
while in plat-omap/dsp/dsp_core.c function  dsp_mbox_init()
asks for "dsp". omap2 is correct, there .name is "dsp".

Patch follows.

There are still some open questions:

Mailbox related:

* Why does

if (IS_ERR(omap_dsp->mbox)) {

in arch/arm/plat-omap/dsp/dsp_core.c in dsp_mbox_init()
doesn't catch NULL pointer (omap_dsp->mbox == NULL)?

- Why does system crash later if omap_dsp->mbox being NULL
is caught correctly? E.g. using

if (omap_dsp->mbox == NULL) {

instead of IS_ERR above results in

...
<3>failed to get mailbox handler for DSP.
<7>omapdsp: unmapping in ARM MMU, v=0xe0fff000, sz=0x1000
<1>Unable to handle kernel paging request at virtual address
b0000ffc
...

LowLevel debug related:

- Why does LowLevel debug only works if omap_writew(reg,
SOFT_REQ_REG) is disabled in mach-omap1/clock.c ?

Cheers

Dirk

      parent reply	other threads:[~2006-10-06  9:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 22:35 Recent git kernels and OSK Philip Balister
2006-10-02 23:29 ` David Brownell
2006-10-03 13:55 ` Dirk Behme
2006-10-03 15:24   ` Dirk Behme
2006-10-04  9:03     ` Dirk Behme
     [not found]       ` <4523892B.3000505@balister.org>
2006-10-04 13:27         ` Dirk Behme
2006-10-06  9:58       ` Dirk Behme [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=452628BA.4000907@gmail.com \
    --to=dirk.behme@googlemail.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