linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylylov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: alan@lxorguk.ukuu.org.uk, B.Zolnierkiewicz@elka.pw.edu.pl,
	linux-ide@vger.kernel.org
Subject: Re: + fix-ide-dma-resource-managment.patch added to -mm tree
Date: Mon, 27 Mar 2006 15:38:01 +0400	[thread overview]
Message-ID: <4427CE99.6000004@ru.mvista.com> (raw)
In-Reply-To: <4427C467.5030300@ru.mvista.com>

Hello.

Sergei Shtylylov wrote:

> Bartlomiej Zolnierkiewicz wrote:

[skipped]

>>> Resolve several IDE DMA resource management issues:

>>> - release DMA engine for memory mapped DMA as well

>> NAK - this won't work, see siimage.c how these resources were
>> really reserved in the first place [ request_mem_region() ]

    NB: it's reserved this way only when available -- this driver can work 
with both I/O and memory mapped regs...

>    Oops, looks like I missed that missing ide_setup_dma() call in that 
> driver...

    No, I've just forgotten that it's called implicitly from setup-pci.c since 
init_dma() "method" in not defined in that driver. So, looks like you're wrong 
here -- it should work currently BUT the DMA engine is not released since 
(mmio == 2) check and return precedes call to ide_release_dma_engine() in 
ide_release_dma().
    And as I said, there's no provision to release any driver-specific 
resources on a call to ide_release_dma()...

[skipped]

>> hwif->mmio == 2 means that host driver is responsible
>> for reserving/releasing resources (this is _preferred_ way
>> of handling resources)

>    Hm, didn't know that...

    ... and this was hard to guess from the current code. ;-)

>> please fix trm290.c to use ->mmio == 2 instead

>    It's a _really_ old chipset (pre SFF-8038i) and has _no_ memory 
> mapped regs AFAIK...

    The only thing that can be done is not to call ide_setup_dma() from it...

>>> - release the channel's secondary DMA I/O ports for real

>> NAK, looking and the code - secondary DMA base is only used
>> by siimage.c and sgiioc4.c (both use ->mmio == 2, for siimage ->dma_base2
>> is unused, for sgiioc4 it is used for some weird DMA transfer ending 
>> stuff)

>    Yes, I have sgioc4.c patch that deals with this (almost) ready...

    ... and for siimage, this seems a no-brainer. :-)

[skipped]

WBR, Sergei


  reply	other threads:[~2006-03-27 11:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603212323.k2LNNSnJ006228@shell0.pdx.osdl.net>
     [not found] ` <58cb370e0603261309p126fdc64j1140bbf437ffe06e@mail.gmail.com>
2006-03-27 10:54   ` + fix-ide-dma-resource-managment.patch added to -mm tree Sergei Shtylylov
2006-03-27 11:38     ` Sergei Shtylylov [this message]
2006-03-27 12:21       ` Bartlomiej Zolnierkiewicz
2006-03-27 12:39         ` Sergei Shtylylov
2006-03-27 12:58           ` Bartlomiej Zolnierkiewicz
2006-03-27 13:03             ` Sergei Shtylylov
2006-03-28 13:12       ` Sergei Shtylylov
2006-03-28 14:11         ` Bartlomiej Zolnierkiewicz
2006-03-28 14:20           ` Sergei Shtylylov
2006-03-28 16:21             ` Sergei Shtylylov
2006-03-28 19:26               ` Alan Cox
2006-03-28 19:19                 ` Sergei Shtylylov
2006-03-27 12:07     ` Bartlomiej Zolnierkiewicz
2006-03-27 12:21       ` Sergei Shtylylov
2006-03-27 12:33         ` Bartlomiej Zolnierkiewicz
2006-03-27 12:57           ` Sergei Shtylylov
2006-03-27 13:08             ` Bartlomiej Zolnierkiewicz

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=4427CE99.6000004@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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).