From: Sergei Shtylylov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: alan@lxorguk.ukuu.org.uk, linux-ide@vger.kernel.org
Subject: Re: + fix-ide-dma-resource-managment.patch added to -mm tree
Date: Tue, 28 Mar 2006 20:21:48 +0400 [thread overview]
Message-ID: <4429629C.6060505@ru.mvista.com> (raw)
In-Reply-To: <4429463F.8060604@ru.mvista.com>
Hello.
Sergei Shtylylov wrote:
> Bartlomiej Zolnierkiewicz wrote:
>>> [skipped]
>>>>>>> - 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)
>>> Hm, concerning the other field of ide_hwif_t, dma_master: I
>>> currently see
>>> no users to it but pdc202xx_old.c. The way it's computed makes it
>>> dependent on
>>> what channels are enabled (though all channels are forced present in
>>> that
>>> driver by the most recent patch) which makes it invalid if the
>>> primary channel
>>> happens to be disabled. I'd like to replace it with extra_base fields
>>> which
>>> would point to the extra DMA ports regardless of the channels
>>> present/enabled,
>>> is this OK?
>> Isn't it better to just use pci_resource_start(dev, 4) in pdc202xx_old.c?
> Not only better but is actually correct -- extra_base would belong
> only to a sole channel in a pair... :-< I'm still not sure this field is
> worth introducing... I probably won't.
OTOH, it's handy in ide-dma.c itself. And hwif->extra_base is surely more
efficient than pci_resource_start(hwif->dev, 4). So, I'm going to introduce
it, just changing the initial code somewhat...
WBR, Sergei
next prev parent reply other threads:[~2006-03-28 16:23 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
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 [this message]
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=4429629C.6060505@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--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).