linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Stanislaw Gruszka <stf_xl@wp.pl>,
	linux-ide@vger.kernel.org, Andrew Victor <linux@maxim.org.za>,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH 2/3] ide: add at91_ide driver
Date: Wed, 04 Feb 2009 19:08:09 +0300	[thread overview]
Message-ID: <4989BD69.5050601@ru.mvista.com> (raw)
In-Reply-To: <4989BC8B.4010105@ru.mvista.com>

Hello, I wrote:

>>>> diff --git a/arch/arm/mach-at91/include/mach/board.h 
>>>> b/arch/arm/mach-at91/include/mach/board.h
>>>> index fb51f0e..6674b9b 100644
>>>> --- a/arch/arm/mach-at91/include/mach/board.h
>>>> +++ b/arch/arm/mach-at91/include/mach/board.h
>>>> @@ -59,6 +59,18 @@ struct at91_cf_data {
>>>> };
>>>> extern void __init at91_add_device_cf(struct at91_cf_data *data);
>>>>
>>>> + /* Compact Flash True IDE mode */
>>>> +struct at91_ide_data {
>>>> +    u8    irq_pin;        /* the same meaning as for CF */

>>>  I again have to express my dislike about not passing IRQ the usual 
>>> way. Also, see my comments to the platform code.

>> Yes, I know, I don't like to argue. Only reasoning to use platform irq 
>> resource
>> seams to be: "because other drivers do". However we have exception - 
>> at91_cf
>> also use board->irq_pin, so maybe this driver could also do ?

>    Then why have the memory resource when we can calculate it from the 
> chip select? (I'm not asking you to do that, since the platfrom device 
> resources are user-visible thru /proc/iomem -- even if the driver is not 
> enabled.)

    Oh, I forgot that it's ARM with its #ifdef hell. :-D
Then they're only visible when the driver is enabled.

MBR, Sergei


  reply	other threads:[~2009-02-04 16:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 10:47 [PATCH 2/3] ide: add at91_ide driver Stanislaw Gruszka
2009-02-04 12:19 ` Sergei Shtylyov
2009-02-04 14:47   ` Stanislaw Gruszka
2009-02-04 16:04     ` Sergei Shtylyov
2009-02-04 16:08       ` Sergei Shtylyov [this message]
2009-02-05 15:01       ` Stanislaw Gruszka
2009-02-05 16:09         ` Sergei Shtylyov
2009-02-05 20:00           ` Andrew Victor
2009-02-05 20:03             ` Sergei Shtylyov
2009-02-06  9:35           ` Stanislaw Gruszka
2009-02-06 10:55           ` Sergei Shtylyov
2009-02-06 16:50             ` Bartlomiej Zolnierkiewicz
2009-02-06 17:20               ` Sergei Shtylyov
2009-02-05 21:23   ` Bartlomiej Zolnierkiewicz
2009-02-05 23:31     ` Sergei Shtylyov
2009-02-06 16:36       ` Bartlomiej Zolnierkiewicz
2009-02-08  0:10         ` Sergei Shtylyov
2009-02-08 11:39           ` Sergei Shtylyov
2009-02-08 22:58             ` Sergei Shtylyov
2009-02-09 19:48               ` Bartlomiej Zolnierkiewicz
2009-02-06  9:30   ` Stanislaw Gruszka
2009-02-06 10:36     ` Sergei Shtylyov
2009-02-06 10:47       ` Stanislaw Gruszka

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=4989BD69.5050601@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@maxim.org.za \
    --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).