All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Mika Westerberg <ext-mika.1.westerberg@nokia.com>,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP2/3/4: DMA: reset controller during init
Date: Mon, 3 May 2010 11:33:16 -0700	[thread overview]
Message-ID: <20100503183316.GY29604@atomide.com> (raw)
In-Reply-To: <87ljc0zvwx.fsf@deeprootsystems.com>

* Kevin Hilman <khilman@deeprootsystems.com> [100503 11:19]:
> Tony Lindgren <tony@atomide.com> writes:
> 
> > * Kevin Hilman <khilman@deeprootsystems.com> [100503 10:00]:
> >> Tony Lindgren <tony@atomide.com> writes:
> >> 
> >> > * Kevin Hilman <khilman@deeprootsystems.com> [100503 08:58]:
> >> >> Mika Westerberg <ext-mika.1.westerberg@nokia.com> writes:
> >> >> 
> >> >> > If we are softbooting another kernel using kexec, DMA controller state is not
> >> >> > known when we are performing omap_init_dma(). It is possible that some DMA
> >> >> > channels are already active. For example after kexec we get:
> >> >> >
> >> >> > <4>IRQ 0020 for non-allocated DMAchannel 5
> >> >> > <4>IRQ 0020 for non-allocated DMAchannel 5
> >> >> > <4>IRQ 0020 for non-allocated DMAchannel 5
> >> >> > <4>IRQ 0020 for non-allocated DMAchannel 5
> >> >> > <4>IRQ 0020 for non-allocated DMAchannel 5
> >> >> >
> >> >> > To prevent any weird things happening, we perform soft reset for the controller
> >> >> > and disable all per channel interrupts.
> >> >> >
> >> >> > Signed-off-by: Mika Westerberg <ext-mika.1.westerberg@nokia.com>
> >> >> 
> >> >> This is a good fix, but we get reset of DMA (and all other blocks) for
> >> >> free when switching to hwmod.  Here's a good reason to convert DMA
> >> >> to hwmod.
> >> >
> >> > Hmm, do we have existing DMA hwmod patches somewhere that work on all omaps?
> >> 
> >> No, that's my point. 
> >> 
> >> Rather than implement reset here (then remove it with DMA hwmods) I'd
> >> rather just see a DMA hwmods added, and then we get reset for free.
> >
> > Sure. But until we have something available we should get the fix part in.
> 
> which will reduce the likelyhood of anyone doing the DMA hwmods until
> some sucker like me does it since nobody else will. :(

Yeah I feel your pain.

Anyways, doing that hwmod change is too late for this coming merge
window if we don't have the patches ready. So we still need to fix
the problem.
 
> I'm just looking for more ways to motivate others to help in hwmod
> conversion.

Yes, and in addition to that at least plat-omap/dma.c, plat-omap/gpio.c
could use some serious clean-up.. And i2c-omap.c too.

Tony

  reply	other threads:[~2010-05-03 18:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 12:55 [PATCH] OMAP2/3/4: DMA: reset controller during init Mika Westerberg
2010-05-03 16:03 ` Kevin Hilman
2010-05-03 16:36   ` Tony Lindgren
2010-05-03 17:05     ` Kevin Hilman
2010-05-03 17:34       ` Tony Lindgren
2010-05-03 18:23         ` Kevin Hilman
2010-05-03 18:33           ` Tony Lindgren [this message]
2010-05-03 16:58 ` Tony Lindgren
2010-05-04  7:40   ` Mika Westerberg
2010-05-11  9:27     ` Mika Westerberg
2010-05-11 15:13       ` Kevin Hilman
2010-05-11 22:29     ` [APPLIED] " 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=20100503183316.GY29604@atomide.com \
    --to=tony@atomide.com \
    --cc=ext-mika.1.westerberg@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    /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.