From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Stanislaw Gruszka <stf_xl@wp.pl>
Cc: linux-ide@vger.kernel.org, Andrew Victor <avictor.za@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH 2/3 v3] ide: add at91_ide driver
Date: Sun, 01 Mar 2009 22:42:41 +0300 [thread overview]
Message-ID: <49AAE531.7020304@ru.mvista.com> (raw)
In-Reply-To: <200902181106.54260.stf_xl@wp.pl>
Hello.
Stanislaw Gruszka wrote:
> This is IDE host driver for AT91 (SAM9, CAP9, AT572D940HF) Static Memory
> Controller with Compact Flash True IDE Mode logic.
>
> Driver have to switch 8/16 bit bus width when accessing Task Tile or Data
> Register. Moreover some extra things need to be done when setting PIO mode.
> Only PIO mode is used, hardware have no DMA support. If interrupt line is
> connected through GPIO extra quirk is needed to cope with fake interrupts.
>
> Signed-off-by: Stanislaw Gruszka <stf_xl@wp.pl>
>
Acked-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> diff --git a/drivers/ide/at91_ide.c b/drivers/ide/at91_ide.c
> new file mode 100644
> index 0000000..1bb50f4
> --- /dev/null
> +++ b/drivers/ide/at91_ide.c
>
[...]
> +static void set_smc_timings(const u8 chipselect, const u16 cycle,
> + const u16 setup, const u16 pulse,
> + const u16 data_float, int use_iordy)
>
This bunch of *const* specifiers is pretty pointless...
> +static void at91_ide_tf_load(ide_drive_t *drive, ide_task_t *task)
> +{
> + ide_hwif_t *hwif = drive->hwif;
> + struct ide_io_ports *io_ports = &hwif->io_ports;
> + struct ide_taskfile *tf = &task->tf;
> + u8 HIHI = (task->tf_flags & IDE_TFLAG_LBA48) ? 0xE0 : 0xEF;
> +
> + if (task->tf_flags & IDE_TFLAG_FLAGGED)
> + HIHI = 0xFF;
> +
> + if (task->tf_flags & IDE_TFLAG_OUT_DATA) {
> + u16 data = (tf->hob_data << 8) | tf->data;
>
It's not quite correct -- should be:
u8 data[2] = { tf->data, tf->hob_data };
Although, if this is a little endian only code, it should be
equivivalent. I shouldn't probably have asked to change this part at
all... :-/
> +static void at91_ide_tf_read(ide_drive_t *drive, ide_task_t *task)
> +{
> + ide_hwif_t *hwif = drive->hwif;
> + struct ide_io_ports *io_ports = &hwif->io_ports;
> + struct ide_taskfile *tf = &task->tf;
> +
> + if (task->tf_flags & IDE_TFLAG_IN_DATA) {
> + u16 data;
>
It would have been easier to just declare it as:
u8 data[2];
> +
> + at91_ide_input_data(drive, NULL, &data, 2);
> + tf->data = data & 0xff;
> + tf->hob_data = (data >> 8) & 0xff;
>
tf->data = data[0];
tf->hob_data = data[1];
MBR, Sergei
next prev parent reply other threads:[~2009-03-01 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 10:06 [PATCH 2/3 v3] ide: add at91_ide driver Stanislaw Gruszka
2009-03-01 19:42 ` Sergei Shtylyov [this message]
2009-03-10 19:21 ` Sergei Shtylyov
2009-03-10 19:24 ` Sergei Shtylyov
2009-03-10 19:29 ` Sergei Shtylyov
2009-03-10 19:31 ` Sergei Shtylyov
2009-03-11 17:00 ` Bartlomiej Zolnierkiewicz
2009-03-13 17:30 ` Sergei Shtylyov
2009-03-13 18:47 ` Bartlomiej Zolnierkiewicz
2009-03-13 19:13 ` 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=49AAE531.7020304@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=avictor.za@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-ide@vger.kernel.org \
--cc=stf_xl@wp.pl \
/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).