From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bob Ham <rah@bash.sh>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 1/2] pata_hpt37x: actually clock HPT374 by 50 MHz DPLL
Date: Mon, 06 Aug 2007 21:16:43 +0400 [thread overview]
Message-ID: <46B7577B.8010003@ru.mvista.com> (raw)
In-Reply-To: <1186419223.23890.3.camel@orchid.arb.net>
Bob Ham wrote:
>>The DPLL tuning code always set up it for 66 MHz due to wrong UltraDMA mask
>>including mode 5 used to check for the necessity of 66 MHz clocking -- This
>>caused 66 MHz clock to be used for HPT374 chip that does not tolerate it.
>>While fixing this, also remove PLL mode from the TODO list -- I don't think
>>it's still relevant item.
>>Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
>>---
>>This is against the current Linus tree.
>>Bob, please test it and report what you'll find out...
> para_hpt37x: bus clock 33MHz, using 50MHz DPLL.
Aha, note that 33 MHz PCI clock is now reported.
> ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 16 (level, low) -> IRQ 17
> scsi2: pata_hpt37x
> scsi3: pata_hpt37x
> ata3: PATA max UDMA/100 cmd 0x0001efa0 ctl 0x0001ef9e bmdma 0x0001ec00 irq 17
> ata4: PATA max UDMA/100 cmd 0x0001ef90 ctl 0x0001ef9a bmdma 0x0001ec00 irq 17
> followed by a hard lock
Well, so it's tougher than just that but the patches are good anyway.
Wait... doesn't it get stuck trying to pick up the HPT374 chip's function 1?
MBR, Sergei
next prev parent reply other threads:[~2007-08-06 17:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 18:45 [PATCH 1/2] pata_hpt37x: actually clock HPT374 by 50 MHz DPLL Sergei Shtylyov
2007-08-05 19:23 ` Alan Cox
2007-08-08 0:49 ` Jeff Garzik
2007-08-08 1:17 ` Alan Cox
2007-08-08 1:22 ` Jeff Garzik
2007-08-08 1:41 ` Alan Cox
2007-08-06 16:53 ` Bob Ham
2007-08-06 17:16 ` Sergei Shtylyov [this message]
2007-08-09 20:48 ` Bartlomiej Zolnierkiewicz
2007-08-09 22:52 ` Alan Cox
2007-08-09 23:52 ` Bartlomiej Zolnierkiewicz
2007-08-10 13:24 ` Alan Cox
2007-08-10 15:39 ` Sergei Shtylyov
2007-08-10 15:36 ` Sergei Shtylyov
2007-08-10 15:34 ` 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=46B7577B.8010003@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rah@bash.sh \
/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).