From: Alek Du <alek.du@intel.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: Add Intel SCH PATA support (revised)
Date: Tue, 29 Apr 2008 08:14:11 +0800 [thread overview]
Message-ID: <20080429081411.47fef877@dxy.sh.intel.com> (raw)
In-Reply-To: <200804282101.33012.bzolnier@gmail.com>
Hi Bartlomiej,
On Tue, 29 Apr 2008 03:01:32 +0800
"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com> wrote:
> Re: [PATCH] ata: Add Intel SCH PATA support (revised)
>
> Hi,
>
> On Monday 28 April 2008, Alek Du wrote:
> > Alan,
> >
> > Fixed and tested, please review it:
> >
> > This patch adds Intel SCH chipsets (US15W, US15L, UL11L) PATA controller
> > support.
> >
> > Signed-off-by: Alek Du <alek.du@intel.com>
> > ---
> > drivers/ata/ata_piix.c | 19 +++++++++++++++++++
> > drivers/ide/pci/piix.c | 2 ++
> > include/linux/pci_ids.h | 2 ++
> > 3 files changed, 23 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/ata/ata_piix.c b/drivers/ata/ata_piix.c
> > index ea2c764..4ec4178 100644
> > --- a/drivers/ata/ata_piix.c
> > +++ b/drivers/ata/ata_piix.c
> > @@ -136,6 +136,7 @@ enum piix_controller_ids {
> > ich_pata_33, /* ICH up to UDMA 33 only */
> > ich_pata_66, /* ICH up to 66 Mhz */
> > ich_pata_100, /* ICH up to UDMA 100 */
> > + sch_pata_100, /* SCH up to UDMA 100 */
> > ich5_sata,
> > ich6_sata,
> > ich6m_sata,
> > @@ -216,6 +217,8 @@ static const struct pci_device_id piix_pci_tbl[] = {
> > { 0x8086, 0x269E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
> > /* ICH8 Mobile PATA Controller */
> > { 0x8086, 0x2850, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_100 },
> > + /* Intel SCH PATA Controller */
> > + { 0x8086, 0x811A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, sch_pata_100 },
> >
> > /* NOTE: The following PCI ids must be kept in sync with the
> > * list in drivers/pci/quirks.c.
> > @@ -311,6 +314,13 @@ static struct ata_port_operations ich_pata_ops = {
> > .set_dmamode = ich_set_dmamode,
> > };
> >
> > +static struct ata_port_operations sch_pata_ops = {
> > + .inherits = &piix_pata_ops,
> > + .cable_detect = ata_cable_unknown,
> > + .prereset = ata_sff_prereset,
> > + .set_dmamode = ich_set_dmamode,
> > +};
> > +
> > static struct ata_port_operations piix_sata_ops = {
> > .inherits = &ata_bmdma_port_ops,
> > };
> > @@ -470,6 +480,15 @@ static struct ata_port_info piix_port_info[] = {
> > .port_ops = &ich_pata_ops,
> > },
> >
> > + [sch_pata_100] =
> > + {
> > + .flags = PIIX_PATA_FLAGS | PIIX_FLAG_CHECKINTR,
> > + .pio_mask = 0x1f, /* pio0-4 */
> > + .mwdma_mask = 0x06, /* mwdma1-2 */
> > + .udma_mask = ATA_UDMA5, /* udma0-5 */
> > + .port_ops = &sch_pata_ops,
> > + },
> > +
> > [ich5_sata] =
> > {
> > .flags = PIIX_SATA_FLAGS,
> > diff --git a/drivers/ide/pci/piix.c b/drivers/ide/pci/piix.c
> > index 21c5dd2..31607fe 100644
> > --- a/drivers/ide/pci/piix.c
> > +++ b/drivers/ide/pci/piix.c
> > @@ -380,6 +380,7 @@ static const struct ide_port_info piix_pci_info[] __devinitdata = {
> > /* 22 */ DECLARE_ICH_DEV("ICH4", ATA_UDMA5),
> > /* 23 */ DECLARE_ICH_DEV("ESB2", ATA_UDMA5),
> > /* 24 */ DECLARE_ICH_DEV("ICH8M", ATA_UDMA5),
> > + /* 25 */ DECLARE_ICH_DEV("SCH", ATA_UDMA5),
>
> DECLARE_ICH_DEV() cannot be used here - seems like DEFINE_SCH_DEV()
> needs to be defined (which will lack .enablebits field but otherwise
> be identical to DECLARE_ICH_DEV)
>
I do not understand here, where DECLARE_ICH_DEV() used here? I just defined a new sub_type
sch_pata_100, and inherit most ops from piix instead of cable_detect and prereset.
> also seems that piix_cable_detect() should be updated to check for
> dev->device == PCI_DEVICE_ID_INTEL_SCH_IDE and return ATA_CBL_PATA80
> (it is OK to use it instead of ATA_CBL_UNK in drivers/ide/ - generic
> cable detection code won't override drive side cable detection).
>
My first version of patch is to modify piix_cable_detect like your way. But Alan suggested
use this way -- it is much cleaner. And according to my test, return ATA_CBL_UNK do no harm.
The driver is set to UDMA5 when 80 cable is used.
> otherwise everything looks good
>
> Thanks,
> Bart
Thanks,
Alek
next prev parent reply other threads:[~2008-04-29 0:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 6:00 [PATCH] ata: Add Intel SCH PATA support Alek Du
2008-04-26 9:30 ` Alan Cox
2008-04-26 23:51 ` Alek Du
2008-04-27 8:34 ` Alan Cox
2008-04-27 14:03 ` Alek Du
2008-04-27 14:31 ` Alan Cox
2008-04-28 1:20 ` Alek Du
2008-04-28 9:16 ` Alan Cox
2008-04-29 17:22 ` Sergei Shtylyov
2008-04-28 4:05 ` [PATCH] ata: Add Intel SCH PATA support (revised) Alek Du
2008-04-28 8:41 ` Alan Cox
2008-04-28 9:07 ` Alek Du
2008-04-28 9:21 ` Alan Cox
2008-04-28 19:01 ` Bartlomiej Zolnierkiewicz
2008-04-29 0:14 ` Alek Du [this message]
2008-04-29 3:41 ` Alek Du
2008-04-29 3:39 ` Alek Du
2008-04-29 16:38 ` Sergei Shtylyov
2008-04-30 2:49 ` Alek Du
2008-04-30 11:17 ` Sergei Shtylyov
2008-04-26 16:46 ` [PATCH] ata: Add Intel SCH PATA support Sergei Shtylyov
2008-04-26 23:32 ` Alek Du
2008-04-26 23:50 ` Alan Cox
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=20080429081411.47fef877@dxy.sh.intel.com \
--to=alek.du@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).