linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: linuxppc-dev@ozlabs.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Timur Tabi <timur@freescale.com>,
	Antonino Daplas <adaplas@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsl-diu-fb: Pass the proper device for dma mapping routines
Date: Mon, 6 Apr 2009 09:16:00 -0500	[thread overview]
Message-ID: <4A6C5BFC-C079-4D19-A0FC-992DF2DCF6B4@kernel.crashing.org> (raw)
In-Reply-To: <20090404183120.GA21671@oksana.dev.rtsoft.ru>


On Apr 4, 2009, at 1:31 PM, Anton Vorontsov wrote:

> The driver should pass a device that specifies internal DMA ops, but
> currently NULL pointers are passed, and thus following bug pops up:
>
>  Freescale DIU driver
>  ------------[ cut here ]------------
>  kernel BUG at arch/powerpc/include/asm/dma-mapping.h:237!
>  Oops: Exception in kernel mode, sig: 5 [#1]
>  ...
>  NIP [c01658b4] allocate_buf+0x0/0x8
>  LR [c0306554] fsl_diu_probe+0x2b4/0x518
>  Call Trace:
>  [df02be10] [c030638c] fsl_diu_probe+0xec/0x518 (unreliable)
>  [df02be60] [c020cdec] of_platform_device_probe+0x5c/0x84
>  [df02be80] [c018f5d0] really_probe+0x78/0x1a0
>  [df02bea0] [c018f7c0] __driver_attach+0xa4/0xa8
>  [df02bec0] [c018ea00] bus_for_each_dev+0x60/0x9c
>  [df02bef0] [c018f414] driver_attach+0x24/0x34
>  [df02bf00] [c018f168] bus_add_driver+0x12c/0x1cc
>  [df02bf20] [c018fbdc] driver_register+0x6c/0x110
>  [df02bf30] [c020ccb4] of_register_driver+0x54/0x70
>  [df02bf40] [c03d0a50] fsl_diu_init+0x70/0xa4
>  ...
>
> This patch fixes the issue.
>
> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
> ---
> drivers/video/fsl-diu-fb.c |   34 +++++++++++++++++++++-------------
> 1 files changed, 21 insertions(+), 13 deletions(-)

applied

- k

      reply	other threads:[~2009-04-06 14:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 18:31 [PATCH] fsl-diu-fb: Pass the proper device for dma mapping routines Anton Vorontsov
2009-04-06 14:16 ` Kumar Gala [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=4A6C5BFC-C079-4D19-A0FC-992DF2DCF6B4@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=adaplas@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).