From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/18] ide: add ->read_sff_dma_status method
Date: Sun, 7 Sep 2008 21:23:33 +0200 [thread overview]
Message-ID: <200809072123.33695.bzolnier@gmail.com> (raw)
In-Reply-To: <48C41A2E.8040907@ru.mvista.com>
On Sunday 07 September 2008, Sergei Shtylyov wrote:
> Hello.
>
> Bartlomiej Zolnierkiewicz wrote:
>
> >>> static void ide_tf_load(ide_drive_t *drive, ide_task_t *task)
> >>> {
> >>> ide_hwif_t *hwif = drive->hwif;
> >>>@@ -323,6 +331,8 @@ static void ata_output_data(ide_drive_t
> >>>
> >>> void default_hwif_transport(ide_hwif_t *hwif)
> >>> {
> >>>+ hwif->read_sff_dma_status = ide_read_sff_dma_status;
> >>>+
> >>> hwif->tf_load = ide_tf_load;
> >>> hwif->tf_read = ide_tf_read;
> >>
> >> I also didn't understand the motivation behind putting this method
> >>together with the transport operations... IMO, DMA programming interface
> >>hardly has anything to do with transporting the data over IDE bus.
>
> > The motivation was that hwif->dma_ops is not available yet when
> > ->read_sff_dma_status is used in ide_pci_check_simplex().
>
> > However I agree that it should somehow find its way into ->dma_ops
> > (as usual patches are stongly preffered :).
>
> Unless I'm missing something changing the place where hwif->dma_ops is
> initialized to sff_dma_ops (along the lines it was changed for hwif->dma_base)
> seems pretty trivial, so I wonder why you didn't do it in the same patch...
Indeed, it should be trivial now, one just needs to be careful to:
* move 'if (d->dma_ops) ...' from ide_init_port() into
->init_dma/ide_hwif_setup_dma()
* unset ->dma_ops on ->init_dma/ide_hwif_setup_dma() failures
I guess I overlooked it ATM of making the patch (or the code evolved
greatly in the meantime)...
[ It is really time consuming and difficult to recall the every small
detail of every patch after few months (the patch was posted 10 weeks
ago and merged 6 weeks ago)... The most efficient way of handling
such issues upon discovery is with sending patches... ]
Thanks,
Bart
next prev parent reply other threads:[~2008-09-07 19:26 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 21:33 [PATCH 01/18] ide: add ->read_sff_dma_status method Bartlomiej Zolnierkiewicz
2008-06-20 21:33 ` [PATCH 02/18] ide: use I/O ops directly in ide-dma.c Bartlomiej Zolnierkiewicz
2008-09-08 15:49 ` Sergei Shtylyov
2008-06-20 21:33 ` [PATCH 03/18] ide: remove ->dma_{status,command} fields from ide_hwif_t Bartlomiej Zolnierkiewicz
2008-06-20 21:33 ` [PATCH 04/18] ide: remove ide_setup_dma() Bartlomiej Zolnierkiewicz
2008-06-20 22:03 ` Sergei Shtylyov
2008-06-21 19:06 ` Bartlomiej Zolnierkiewicz
2008-06-21 19:29 ` Sergei Shtylyov
2008-08-21 17:16 ` Sergei Shtylyov
2008-08-21 17:56 ` Sergei Shtylyov
2008-06-20 21:33 ` [PATCH 05/18] ide: factor out simplex handling from ide_pci_dma_base() Bartlomiej Zolnierkiewicz
2008-06-20 21:34 ` [PATCH 06/18] ide: add ->exec_command method Bartlomiej Zolnierkiewicz
2008-06-20 21:34 ` [PATCH 07/18] ide: add ->read_status method Bartlomiej Zolnierkiewicz
2008-06-20 21:34 ` [PATCH 08/18] ide: add ->read_altstatus method Bartlomiej Zolnierkiewicz
2008-06-20 21:34 ` [PATCH 09/18] ide: add ->set_irq method Bartlomiej Zolnierkiewicz
2008-10-15 12:20 ` Sergei Shtylyov
2008-10-15 18:22 ` Bartlomiej Zolnierkiewicz
2008-10-15 21:22 ` Sergei Shtylyov
2008-06-20 21:34 ` [PATCH 10/18] ide: change order of register access in ide_config_drive_speed() Bartlomiej Zolnierkiewicz
2008-06-20 21:34 ` [PATCH 11/18] ide: use ->tf_load " Bartlomiej Zolnierkiewicz
2008-06-20 21:34 ` [PATCH 12/18] ide: use ->tf_load in actual_try_to_identify() Bartlomiej Zolnierkiewicz
2008-06-20 23:14 ` Sergei Shtylyov
2008-06-21 19:10 ` Bartlomiej Zolnierkiewicz
2008-06-20 21:34 ` [PATCH 13/18] ide: use ->tf_load in SELECT_DRIVE() Bartlomiej Zolnierkiewicz
2009-02-15 20:25 ` Sergei Shtylyov
2009-02-16 0:08 ` Sergei Shtylyov
2009-02-16 11:50 ` Sergei Shtylyov
2009-02-16 21:51 ` Bartlomiej Zolnierkiewicz
2009-02-17 1:04 ` Sergei Shtylyov
2009-02-17 14:43 ` Bartlomiej Zolnierkiewicz
2009-02-17 15:32 ` Sergei Shtylyov
2009-03-04 15:43 ` Sergei Shtylyov
2009-02-17 12:23 ` Sergei Shtylyov
2009-02-17 15:13 ` Sergei Shtylyov
2008-06-20 21:34 ` [PATCH 14/18] ide: use ->tf_read in ide_read_error() Bartlomiej Zolnierkiewicz
2009-02-15 23:21 ` Sergei Shtylyov
2009-02-16 12:13 ` Sergei Shtylyov
2009-02-16 12:25 ` Sergei Shtylyov
2009-02-16 21:17 ` Bartlomiej Zolnierkiewicz
2009-02-17 0:14 ` Sergei Shtylyov
2009-02-17 0:50 ` Sergei Shtylyov
2008-06-20 21:35 ` [PATCH 15/18] ide: add ide_read_device() helper Bartlomiej Zolnierkiewicz
2008-06-20 21:35 ` [PATCH 16/18] ide: add ide_read_ireason() helper Bartlomiej Zolnierkiewicz
2008-06-20 21:35 ` [PATCH 17/18] ide: add ide_read_bcount_and_ireason() helper Bartlomiej Zolnierkiewicz
2008-06-20 21:35 ` [PATCH 18/18] ide: remove ->INB, ->OUTB and ->OUTBSYNC methods Bartlomiej Zolnierkiewicz
2008-09-03 13:19 ` [PATCH 01/18] ide: add ->read_sff_dma_status method Sergei Shtylyov
2008-09-03 18:13 ` Bartlomiej Zolnierkiewicz
2008-09-07 18:15 ` Sergei Shtylyov
2008-09-07 18:49 ` Sergei Shtylyov
2008-09-07 19:23 ` Bartlomiej Zolnierkiewicz [this message]
2008-09-07 22:26 ` Sergei Shtylyov
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=200809072123.33695.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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).