linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khc@pm.waw.pl (Krzysztof Halasa)
To: linux-arm-kernel@lists.infradead.org
Subject: IXP4xx: unneeded #include platform-specific include files?
Date: Tue, 17 Nov 2009 23:22:21 +0100	[thread overview]
Message-ID: <m3skcc4wrm.fsf@intrepid.localdomain> (raw)
In-Reply-To: <op.u3j7xuh92s3iss@richese> (Imre Kaloz's message of "Tue, 17 Nov 2009 23:11:44 +0100")

"Imre Kaloz" <kaloz@openwrt.org> writes:

> Why wouldn't you want to remember that "INTA" was "GPIO8"? When you want to
> touch those lines you do have to remember or look up what GPIO was that one.
> So this hardly makes it easier to work with or to remember to -- it certainly
> duplicates the assignments, as you've also noted.

Actually I'm not sure if I understand you correctly.

If I use GPIO8 (presumably in different places) I have to remember what
it is. This may be use with a couple of IRQ lines but gets harder and
harder with a more complicated machine. Macros like SLOT0_INTA etc.
don't have this problem. That's BTW why macros and symbolic names were
invented.

> The INTx naming convention is also stupid, as in most cases these are
> not different
> INT lines of the PCI slot but either separate slots or subdevices -- and note,
> most of the boards only have INTa connected mechanically.
>
> And I didn't even get to the topic of *_PCI_MAX_DEV, *_PCI_IRQ_LINES
> and the mania
> of pci_irq_table usage..

But you've seen the patches I just posted, haven't you?
-- 
Krzysztof Halasa

  reply	other threads:[~2009-11-17 22:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 17:16 IXP4xx: unneeded #include platform-specific include files? Krzysztof Halasa
2009-11-15 18:27 ` Mikael Pettersson
2009-11-15 20:18   ` Imre Kaloz
2009-11-15 21:14     ` Krzysztof Halasa
2009-11-17 21:37       ` Imre Kaloz
2009-11-17 21:53         ` Krzysztof Halasa
2009-11-17 22:11           ` Imre Kaloz
2009-11-17 22:22             ` Krzysztof Halasa [this message]
2009-11-17 22:34               ` Imre Kaloz
2009-11-17 22:47                 ` Krzysztof Halasa
2009-11-17 23:05                   ` Imre Kaloz
2009-11-18  0:10                     ` Krzysztof Halasa
2009-11-15 18:41 ` Mike Westerhof

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=m3skcc4wrm.fsf@intrepid.localdomain \
    --to=khc@pm.waw.pl \
    --cc=linux-arm-kernel@lists.infradead.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).