From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 07/28] ARM: iop13xx: move io.h externs to io.c
Date: Wed, 29 Feb 2012 16:16:36 -0600 [thread overview]
Message-ID: <4F4EA3C4.8000706@gmail.com> (raw)
In-Reply-To: <201202292147.39302.arnd@arndb.de>
I dropped some CC's as I'm getting bounced.
On 02/29/2012 03:47 PM, Arnd Bergmann wrote:
> On Wednesday 29 February 2012, Rob Herring wrote:
>> arch/arm/mach-iop13xx/include/mach/io.h | 4 ----
>> arch/arm/mach-iop13xx/io.c | 5 +++++
>> 2 files changed, 5 insertions(+), 4 deletions(-)
>
> Moving them out of io.h is good, but moving declarations into a .c file
> is rather bad style. It should remain in a header file that is visible to
> both io.c and pci.c. mach/pci.h would be an obvious choice.
Yes I know, but it was only in 1 place. I'll add a mach-iop13xx/pci.h.
> I'm also not sure if the iop13xx magic ioremap stuff is really needed
> and worth keeping. You mentioned in the description for patch 6 that
> it's used for 64 bit address mapping, but I can't see that in the code.
> Where did you find that information?
>
Look at the ULL defines:
#define IOP13XX_PCIX_MEM_PHYS_OFFSET 0x100000000ULL
#define IOP13XX_PCIX_MEM_WINDOW_SIZE 0x3a000000UL
#define IOP13XX_PCIX_LOWER_MEM_BA (PHYS_OFFSET + IOP13XX_PCI_OFFSET)
#define IOP13XX_PCIX_LOWER_MEM_PA (IOP13XX_PCIX_MEM_PHYS_OFFSET +\
IOP13XX_PCIX_LOWER_MEM_BA)
There's also this discussion (search the page for iop13xx):
http://comments.gmane.org/gmane.linux.ports.arm.kernel/30905
Rob
next prev parent reply other threads:[~2012-02-29 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1330547147-22867-1-git-send-email-robherring2@gmail.com>
[not found] ` <1330547147-22867-17-git-send-email-robherring2@gmail.com>
2012-02-29 20:40 ` [PATCH v2 16/28] ARM: remove bunch of now unused mach/io.h files H Hartley Sweeten
[not found] ` <1330547147-22867-16-git-send-email-robherring2@gmail.com>
2012-02-29 20:43 ` [PATCH v2 15/28] ARM: make mach/io.h include optional H Hartley Sweeten
[not found] ` <1330547147-22867-8-git-send-email-robherring2@gmail.com>
[not found] ` <201202292147.39302.arnd@arndb.de>
2012-02-29 22:16 ` Rob Herring [this message]
2012-02-29 22:26 ` [PATCH v2 07/28] ARM: iop13xx: move io.h externs to io.c Arnd Bergmann
[not found] ` <1330547147-22867-20-git-send-email-robherring2@gmail.com>
[not found] ` <201202292153.03056.arnd@arndb.de>
2012-02-29 22:28 ` [PATCH v2 19/28] ARM: Add fixed PCI i/o mapping Rob Herring
2012-02-29 22:43 ` Arnd Bergmann
2012-02-29 23:21 ` Russell King - ARM Linux
2012-03-01 13:52 ` Arnd Bergmann
2012-03-01 14:08 ` Russell King - ARM Linux
2012-03-01 18:25 ` Arnd Bergmann
2012-03-01 20:32 ` Andrew Lunn
2012-03-05 20:24 ` Nicolas Pitre
[not found] ` <20120229221341.GF16999@n2100.arm.linux.org.uk>
2012-03-01 4:11 ` Rob Herring
[not found] ` <1330547147-22867-4-git-send-email-robherring2@gmail.com>
[not found] ` <201202292134.03220.arnd@arndb.de>
2012-02-29 22:55 ` [PATCH v2 03/28] ARM: imx: convert to common runtime ioremap hook Rob Herring
2012-02-29 23:13 ` Arnd Bergmann
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=4F4EA3C4.8000706@gmail.com \
--to=robherring2@gmail.com \
--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).