LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] ide: merge ->atapi_*put_bytes and ->ata_*put_data methods
Date: Thu, 05 Mar 2009 16:12:59 +0300 [thread overview]
Message-ID: <49AFCFDB.9080203@ru.mvista.com> (raw)
In-Reply-To: <200803302141.03013.bzolnier@gmail.com>
Hello.
Bartlomiej Zolnierkiewicz wrote:
> * Merge ->atapi_{in,out}put_bytes and ->ata_{in,out}put_data methods
> into new ->{in,out}put_data methods which take number of bytes to
> transfer as an argument and always do padding.
> While at it:
> * Use 'hwif' or 'drive->hwif' instead of 'HWIF(drive)'.
> There should be no functional changes caused by this patch (all users
> of ->ata_{in,out}put_data methods were using multiply-of-4 word counts).
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Congratulations -- you introduced a bug with this patch. ;-)
> Index: b/drivers/ide/ide-iops.c
> ===================================================================
> --- a/drivers/ide/ide-iops.c
> +++ b/drivers/ide/ide-iops.c
> @@ -191,34 +191,45 @@ static void ata_vlb_sync(ide_drive_t *dr
>
> /*
> * This is used for most PIO data transfers *from* the IDE interface
> + *
> + * These routines will round up any request for an odd number of bytes,
> + * so if an odd len is specified, be sure that there's at least one
> + * extra byte allocated for the buffer.
> */
> -static void ata_input_data(ide_drive_t *drive, void *buffer, u32 wcount)
> +static void ata_input_data(ide_drive_t *drive, void *buf, unsigned int len)
> {
> ide_hwif_t *hwif = drive->hwif;
> struct ide_io_ports *io_ports = &hwif->io_ports;
> + unsigned long data_addr = io_ports->data_addr;
> u8 io_32bit = drive->io_32bit;
>
> + len++;
> +
Now where is the symmetric len++ in ata_output_data()?
> if (io_32bit) {
> if (io_32bit & 2) {
> unsigned long flags;
>
> local_irq_save(flags);
> ata_vlb_sync(drive, io_ports->nsect_addr);
> - hwif->INSL(io_ports->data_addr, buffer, wcount);
> + hwif->INSL(data_addr, buf, len / 4);
> local_irq_restore(flags);
> } else
> - hwif->INSL(io_ports->data_addr, buffer, wcount);
> + hwif->INSL(data_addr, buf, len / 4);
> +
> + if ((len & 3) >= 2)
> + hwif->INSW(data_addr, (u8 *)buf + (len & ~3), 1);
> } else
> - hwif->INSW(io_ports->data_addr, buffer, wcount << 1);
> + hwif->INSW(data_addr, buf, len / 2);
> }
>
> /*
> * This is used for most PIO data transfers *to* the IDE interface
> */
> -static void ata_output_data(ide_drive_t *drive, void *buffer, u32 wcount)
> +static void ata_output_data(ide_drive_t *drive, void *buf, unsigned int len)
> {
> ide_hwif_t *hwif = drive->hwif;
> struct ide_io_ports *io_ports = &hwif->io_ports;
> + unsigned long data_addr = io_ports->data_addr;
> u8 io_32bit = drive->io_32bit;
>
> if (io_32bit) {
Patch coming. It turned out to be really good thing that I decided to look
into these methods...
MBR, Sergei
prev parent reply other threads:[~2009-03-05 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 19:41 Bartlomiej Zolnierkiewicz
2009-03-05 13:12 ` Sergei Shtylyov [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=49AFCFDB.9080203@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH 1/6] ide: merge ->atapi_*put_bytes and ->ata_*put_data methods' \
/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
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).