linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] ata_piix: unify code for programming PIO and MWDMA timings
Date: Fri, 14 Oct 2011 16:01:48 +0400	[thread overview]
Message-ID: <4E9824AC.6020902@mvista.com> (raw)
In-Reply-To: <201110131539.11190.bzolnier@gmail.com>

Hello.

On 13-10-2011 17:39, Bartlomiej Zolnierkiewicz wrote:

> From: Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>
> Subject: [PATCH v2] ata_piix: unify code for programming PIO and MWDMA timings

> Besides making things noticably simpler it results in ~2% decrease in
> the driver LOC count and also ~2% decrease in the driver binary size
> (as measured on x86-32).

> Fix piix_set_piomode() documentation while at it.

> Signed-off-by: Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>

    I'm still inclined to NAK this patch.

> ---
> v2: remove use_mwdma variable and fix comment style

> earlier references:
> https://lkml.org/lkml/2011/2/8/99
>
>   drivers/ata/ata_piix.c |  111 ++++++++++++++++---------------------------------
>   1 file changed, 38 insertions(+), 73 deletions(-)

> Index: b/drivers/ata/ata_piix.c
> ===================================================================
> --- a/drivers/ata/ata_piix.c
> +++ b/drivers/ata/ata_piix.c
[...]
> @@ -811,31 +822,20 @@ static void do_pata_set_dmamode(struct a
[...]
> -	if (ap->udma_mask)
> -		pci_read_config_byte(dev, 0x48,&udma_enable);

    Don't think you should remove this.

> -
>   	if (speed>= XFER_UDMA_0) {
> -		unsigned int udma = adev->dma_mode - XFER_UDMA_0;
> +		unsigned int udma = speed - XFER_UDMA_0;
>   		u16 udma_timing;
>   		u16 ideconf;
>   		int u_clock, u_speed;
>
> +		spin_lock_irqsave(&piix_lock, flags);
> +
> +		pci_read_config_byte(dev, 0x48, &udma_enable);

    But you should also clear the UDMA enable bit when setting an MWDMA mode, no?

> +
>   		/*
>   		 * UDMA is handled by a combination of clock switching and
>   		 * selection of dividers
> @@ -868,56 +868,21 @@ static void do_pata_set_dmamode(struct a
>   			   performance (WR_PingPong_En) */
>   			pci_write_config_word(dev, 0x54, ideconf);
>   		}
> +
> +		pci_write_config_byte(dev, 0x48, udma_enable);
> +
> +		spin_unlock_irqrestore(&piix_lock, flags);
>   	} else {
> -		/*
> -		 * MWDMA is driven by the PIO timings. We must also enable
> -		 * IORDY unconditionally along with TIME1. PPE has already
> -		 * been set when the PIO timing was set.
> -		 */
> -		unsigned int mwdma	= adev->dma_mode - XFER_MW_DMA_0;
> -		unsigned int control;
> -		u8 slave_data;
> +		/* MWDMA is driven by the PIO timings. */
> +		unsigned int mwdma = speed - XFER_MW_DMA_0;
>   		const unsigned int needed_pio[3] = {
>   			XFER_PIO_0, XFER_PIO_3, XFER_PIO_4
>   		};
>   		int pio = needed_pio[mwdma] - XFER_PIO_0;
>
[...]
> -		if (ap->udma_mask)
> -			udma_enable&= ~(1<<  devid);

    Still don't understand why you're removing this code.

> -
> -		pci_write_config_word(dev, master_port, master_data);
> +		/* XFER_PIO_0 is never used currently */
> +		piix_set_timings(ap, adev, pio);
>   	}
> -	/* Don't scribble on 0x48 if the controller does not support UDMA */
> -	if (ap->udma_mask)
> -		pci_write_config_byte(dev, 0x48, udma_enable);

    Should have kept this one too...

MBR, Sergei

  reply	other threads:[~2011-10-14 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 13:39 [PATCH v2 2/4] ata_piix: unify code for programming PIO and MWDMA timings Bartlomiej Zolnierkiewicz
2011-10-14 12:01 ` Sergei Shtylyov [this message]
2011-10-14 13:43   ` Bartlomiej Zolnierkiewicz
2011-10-14 16:43     ` Sergei Shtylyov
2011-10-14 16:51       ` 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=4E9824AC.6020902@mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=bzolnier@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).