From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-ide <linux-ide@vger.kernel.org>,
622997@bugs.debian.org
Subject: Re: libata-sff/pata_cmd64x problem with hardwired configurations
Date: Tue, 19 Apr 2011 11:20:30 +0200 [thread overview]
Message-ID: <201104191120.31061.bzolnier@gmail.com> (raw)
In-Reply-To: <4DAC63EA.4000707@ru.mvista.com>
Hi,
Sergei Shtylyov wrote:
> Hello.
>
> James Bottomley wrote:
>
> >>> I can get all of this working by fixing up all the hard coded knowledge
> >>> in libata-sff only to use a single port.
> >>> However, I can't fix the libata-sff driver until I know how to tell
> >>> there's only one port wired. Does anyone with cmd649 knowledge have any
> >>> idea how I might tell this?
>
> >> The secondary port is enabled in the PCI config. space: register 0x51 bit
> >> 3 controls this. Unfortunately, pata_cmd64x driver still doesn't check the
> >> channel enable bits; the cmd64x driver does though, so it might be worth trying...
>
> > So this is the enablebits code in driver/ide
>
> We still need to ensure that these are indeed the enable bits that are at
> play here...
>
> > that's missing from any of
> > the libata stuff?
>
> Not from any. It's handled in some drivers, like pata_hpt37x, for example --
> in their prereset() methods.
>
> > Should this be generic in libata-sff? ...
>
> There's even libata core function, pci_test_config_bits() that facilitates
> this check.
>
> > I mean even on an x86 where arbitrary memory can be poked without consequence,
> > trying to activate a disabled port will still produce lots of noise.
>
> The story with pata_cmd64x is somewhat convoluted: originally (when the
> libata driver was created) in the IDE driver there were only enable bits for the
> secondary channel of PCI0646 (and even those wrong); I fixed those and added the
> enable bits for other chips back in 2007 but it never got propagated to
> pata_cmd64x. Well, I have some plans for changes to this driver but not much
> time to actually do them currently...
>From atang tree, orginally posted in 2009:
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: [PATCH v2] pata_cmd64x: add enablebits checking
Fixes IDE -> libata regression.
IDE's cmd64x host driver has been supporting enablebits checking
since the initial driver's merge.
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
---
drivers/ata/pata_cmd64x.c | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
Index: b/drivers/ata/pata_cmd64x.c
===================================================================
--- a/drivers/ata/pata_cmd64x.c
+++ b/drivers/ata/pata_cmd64x.c
@@ -79,6 +79,40 @@ static int cmd648_cable_detect(struct at
}
/**
+ * cmd64x_prereset - perform reset handling
+ * @link: ATA link
+ * @deadline: deadline jiffies for the operation
+ *
+ * Reset sequence checking enable bits to see which ports are
+ * active.
+ */
+
+static int cmd64x_prereset(struct ata_link *link, unsigned long deadline)
+{
+ static const struct pci_bits cmd64x_enable_bits[] = {
+ { 0x51, 1, 0x04, 0x04 },
+ { 0x51, 1, 0x08, 0x08 }
+ };
+
+ struct ata_port *ap = link->ap;
+ struct pci_dev *pdev = to_pci_dev(ap->host->dev);
+
+ /*
+ * The original PCI0643 and PCI0646 didn't have the primary
+ * channel enable bit, it appeared starting with PCI0646U
+ * (i.e. revision ID 3).
+ */
+ if (ap->port_no == 0 && (pdev->device == PCI_DEVICE_ID_CMD_643 ||
+ (pdev->device == PCI_DEVICE_ID_CMD_646 && pdev->revision < 3)))
+ goto out;
+
+ if (!pci_test_config_bits(pdev, &cmd64x_enable_bits[ap->port_no]))
+ return -ENOENT;
+out:
+ return ata_sff_prereset(link, deadline);
+}
+
+/**
* cmd64x_set_timing - set PIO and MWDMA timing
* @ap: ATA interface
* @adev: ATA device
@@ -266,6 +300,7 @@ static const struct ata_port_operations
.inherits = &ata_bmdma_port_ops,
.set_piomode = cmd64x_set_piomode,
.set_dmamode = cmd64x_set_dmamode,
+ .prereset = cmd64x_prereset,
};
static struct ata_port_operations cmd64x_port_ops = {
next prev parent reply other threads:[~2011-04-19 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 23:58 libata-sff/pata_cmd64x problem with hardwired configurations James Bottomley
2011-04-18 10:12 ` Sergei Shtylyov
2011-04-18 15:55 ` James Bottomley
2011-04-18 16:16 ` Sergei Shtylyov
2011-04-19 9:20 ` Bartlomiej Zolnierkiewicz [this message]
2011-04-19 10:08 ` Alan Cox
2011-04-19 11:50 ` Bartlomiej Zolnierkiewicz
2011-04-19 12:29 ` Alan Cox
2011-04-19 13:59 ` James Bottomley
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=201104191120.31061.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=622997@bugs.debian.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@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