From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: bzolnier@gmail.com, linux-mips@linux-mips.org,
linux-ide@vger.kernel.org, ralf@linux-mips.org
Subject: Re: [PATCH 1/2] ide: Add tx4939ide driver (v2)
Date: Wed, 24 Sep 2008 22:26:32 +0400 [thread overview]
Message-ID: <48DA8658.2040107@ru.mvista.com> (raw)
In-Reply-To: <48DA2543.4050304@ru.mvista.com>
Hello, I wrote:
>>>> +static void tx4939ide_tf_load(ide_drive_t *drive, ide_task_t *task)
>>>> +{
>>>> + mm_tf_load(drive, task);
>>>> + if (task->tf_flags & IDE_TFLAG_OUT_DEVICE) {
>>>> + ide_hwif_t *hwif = drive->hwif;
>>>> + void __iomem *base = TX4939IDE_BASE(hwif);
>>>> + /* Fix ATA100 CORE System Control Register */
>>>> + tx4939ide_writew(tx4939ide_readw(base, TX4939IDE_Sys_Ctl) &
>>>> + 0x07f0,
>>>> + base, TX4939IDE_Sys_Ctl);
>>> Why? Doesn't page 17-4 of the datasheet say that these bits get
>>> auto-cleared ona write to the device/head register? Or is this to
>>> address <CAUSION> on page 17-9?
>> Yes, that "CAUSION". I will put it in the comment.
> Frankly speaking, I couldn't make out much of tht passage:
> <CAUSION>
> The write to the register by the Device/Head register may cause an
> unexpected function by write wrong
> data to the register. So please rewrite to the System Control register
> after write to the Device/Head
> register to secure write to System Control register in ATA100 Core.
I thought that this was related to loading the correct transfer mode for
the selected drive. But if it's not only that, it would be quite pointless to
also implement selectproc() method if you have to hook the tf_load() method...
Frankly speaking, I don't understand why they didn't implement 2 timing
registers like on TC86C001 while still implementing 2 transfer counter
registers...
MBR, Sergei
next prev parent reply other threads:[~2008-09-24 18:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 15:13 [PATCH 1/2] ide: Add tx4939ide driver (v2) Atsushi Nemoto
2008-09-17 21:58 ` Jeff Garzik
2008-09-18 16:10 ` Atsushi Nemoto
2008-09-18 23:45 ` Bartlomiej Zolnierkiewicz
2008-09-19 9:25 ` Sergei Shtylyov
2008-09-19 17:10 ` Bartlomiej Zolnierkiewicz
2008-09-20 18:26 ` Sergei Shtylyov
2008-09-20 21:59 ` Sergei Shtylyov
2008-09-21 9:21 ` Sergei Shtylyov
2008-09-21 16:32 ` Atsushi Nemoto
2008-09-24 11:32 ` Sergei Shtylyov
2008-09-24 18:26 ` Sergei Shtylyov [this message]
2008-09-25 13:41 ` Atsushi Nemoto
2008-09-25 13:16 ` Atsushi Nemoto
2008-09-23 17:04 ` Atsushi Nemoto
2008-09-23 17:20 ` Sergei Shtylyov
2008-09-27 16:19 ` 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=48DA8658.2040107@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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).