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 6/6] ide: rework handling of serialized ports
Date: Tue, 04 Nov 2008 21:30:10 +0300 [thread overview]
Message-ID: <491094B2.4090107@ru.mvista.com> (raw)
In-Reply-To: <20081103200326.5098.2058.sendpatchset@localhost.localdomain>
Bartlomiej Zolnierkiewicz wrote:
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Subject: [PATCH] ide: rework handling of serialized ports
> * hpt366: set IDE_HFLAG_SERIALIZE in hwif->host_flags if needed
> in init_hwif_hpt366(). Remove HPT_SERIALIZE_IO while at it.
> * Set IDE_HFLAG_SERIALIZE in hwif->host_flags if needed in
> ide_init_port().
> * Convert init_irq() to use IDE_HFLAG_SERIALIZE together with
> hwif->host to find out ports which need to be serialized.
> * Remove no longer needed save_match() and ide_hwif_t.serialized.
> This patch should fix the incorrect grouping of port(s) from
> host(s) that need serialization with port(s) that happen to use
> the same IRQ(s) but are from the host(s) that don't need it.
> Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Acked-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> static int __devinit init_dma_hpt366(ide_hwif_t *hwif,
> Index: b/drivers/ide/ide-probe.c
> ===================================================================
> --- a/drivers/ide/ide-probe.c
> +++ b/drivers/ide/ide-probe.c
[...]
> + if (hwif->host_flags & IDE_HFLAG_SERIALIZE) {
> + if (hwif->host == h->host)
> + match = h;
Can be collapsed into a single *if*, and braces not needed either way.
> @@ -1436,10 +1398,8 @@ static void ide_init_port(ide_hwif_t *hw
> }
>
> if ((d->host_flags & IDE_HFLAG_SERIALIZE) ||
> - ((d->host_flags & IDE_HFLAG_SERIALIZE_DMA) && hwif->dma_base)) {
> - if (hwif->mate)
> - hwif->mate->serialized = hwif->serialized = 1;
> - }
> + ((d->host_flags & IDE_HFLAG_SERIALIZE_DMA) && hwif->dma_base))
> + hwif->host_flags |= IDE_HFLAG_SERIALIZE;
I don't see what use is forcing this flag at all here -- it doesn't seem
to be checked only in init_irq() now, so this *if* could just be moved there...
MBR, Sergei
next prev parent reply other threads:[~2008-11-04 18:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 20:02 [PATCH 1/6] ide: fix ->quirk_list checking in ide_do_request() Bartlomiej Zolnierkiewicz
2008-11-03 20:02 ` [PATCH 2/6] ide: always set nIEN on idle devices Bartlomiej Zolnierkiewicz
2008-11-03 20:03 ` [PATCH 3/6] rz1000: apply chipset quirks early Bartlomiej Zolnierkiewicz
2008-11-04 17:18 ` Sergei Shtylyov
2008-11-04 18:56 ` Sergei Shtylyov
2008-11-09 14:03 ` Bartlomiej Zolnierkiewicz
2008-11-03 20:03 ` [PATCH 4/6] trm290: add IDE_HFLAG_TRM290 host flag Bartlomiej Zolnierkiewicz
2008-11-04 17:36 ` Sergei Shtylyov
2008-11-03 20:03 ` [PATCH 5/6] cy82c693: remove superfluous ide_cy82c693 chipset type Bartlomiej Zolnierkiewicz
2008-11-03 20:03 ` [PATCH 6/6] ide: rework handling of serialized ports Bartlomiej Zolnierkiewicz
2008-11-04 18:30 ` Sergei Shtylyov [this message]
2008-11-04 18:34 ` Sergei Shtylyov
2008-11-09 14:04 ` 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=491094B2.4090107@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.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).