linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: list linux-ide <linux-ide@vger.kernel.org>
Subject: Re: DMA breakage in 2.6.29-rc*
Date: Mon, 02 Feb 2009 09:49:12 +1100	[thread overview]
Message-ID: <1233528552.18767.62.camel@pasglop> (raw)
In-Reply-To: <200902011744.07794.bzolnier@gmail.com>


> Yeah my bad, though thanks to Andreas Schwab it is fixed in -rc3.

Hrm... I was using rc3 here and had the bug. I'll dig to check it's
really that or something else and send a patch if needed.

> Would be great as I have completely no idea about this stuff.

No worries.

> While you are at DMA support and will be fixing/testing it anyway
> you may try to remove long standing duplication/obfuscation:
> 
> 	/* Those fields are duplicating what is in hwif. We currently
> 	 * can't use the hwif ones because of some assumptions that are
> 	 * beeing done by the generic code about the kind of dma controller
> 	 * and format of the dma table. This will have to be fixed though.
> 	 */
> 	volatile struct dbdma_regs __iomem *	dma_regs;
> 	struct dbdma_cmd*		dma_table_cpu;
> 
> What needs to be done is more-or-less:
> 
> - teaching pmac_ide_init_dma() about hwif->prd_max_{nents,size}
>   and then converting it to use ide_allocate_dma_engine()
> 
> - pmif->dma_regs -> hwif->dma_base
> 
> - pmif->dma_table_cpu -> hwif->dmatable_cpu
> 
> - sticking ide_release_dma_engine() somewhere (it seems that
>   pmac driver never frees DMA memory allocated currently)

I'll have a look. Can't promise I'll get it all done this week tho. I
have several other urgent things on my plate.

> Of course while the above would be a nice cleanup+fixup, making
> the driver work comes first..

Heh, we'll see... ide-pmac was never quite intended as a module and
definitely not a module you can remove. I don't know if it's worth
fixing to be honest.

Cheers,
Ben.

> Thanks,
> Bart


  reply	other threads:[~2009-02-01 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30  5:46 DMA breakage in 2.6.29-rc* Benjamin Herrenschmidt
2009-01-30 11:07 ` Benjamin Herrenschmidt
2009-02-01 16:44   ` Bartlomiej Zolnierkiewicz
2009-02-01 22:49     ` Benjamin Herrenschmidt [this message]
2009-02-01 23:07       ` Benjamin Herrenschmidt
2009-01-30 12:17 ` Mikael Pettersson
2009-01-30 20:45   ` Benjamin Herrenschmidt

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=1233528552.18767.62.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@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 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).