From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Greg Kroah-Hartman <greg@kroah.com>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Olof Johannsson <olof@lixom.net>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 6/7] Enable MSI mappings for MPIC
Date: Thu, 11 Jan 2007 16:22:22 +0100 [thread overview]
Message-ID: <b359a2c351f628252dc385285911d37e@kernel.crashing.org> (raw)
In-Reply-To: <20070111112507.E775CDDF0E@ozlabs.org>
> + flags = readb(base + HT_MSI_FLAGS);
> + if (!(flags & HT_MSI_FLAGS_FIXED)) {
> + addr = readl(base + HT_MSI_ADDR_LO) & HT_MSI_ADDR_LO_MASK;
> + addr = addr | ((u64)readl(base + HT_MSI_ADDR_HI) << 32);
> + }
> +
> + printk(KERN_INFO "mpic: - HT:%02x.%x %s MSI mapping found @
> 0x%lx\n",
> + PCI_SLOT(devfn), PCI_FUNC(devfn),
> + flags & HT_MSI_FLAGS_ENABLE ? "enabled" : "disabled", addr);
It's not safe in general to just take what the hardware
is currently set to.
Perhaps it is best to just always program 0xfee00000 (it's
a per-bus thing so you can use the same address everywhere),
since that address *has* to not conflict with other mappings
already, it being the standard fixed address and everything.
Segher
next prev parent reply other threads:[~2007-01-11 15:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 11:25 [PATCH 0/7] Powerpc MSI Implementation Michael Ellerman
2007-01-11 11:25 ` [PATCH 1/7] Rip out the existing powerpc msi stubs Michael Ellerman
2007-01-11 21:31 ` Christoph Hellwig
2007-01-11 11:25 ` [PATCH 2/7] Powerpc MSI implementation Michael Ellerman
2007-01-11 19:44 ` Greg KH
2007-01-11 21:20 ` Benjamin Herrenschmidt
2007-01-11 21:54 ` Benjamin Herrenschmidt
2007-01-12 23:13 ` Greg KH
2007-01-13 5:57 ` Benjamin Herrenschmidt
2007-01-13 19:27 ` Greg KH
2007-01-13 20:40 ` Benjamin Herrenschmidt
2007-01-12 23:11 ` Greg KH
2007-01-11 21:36 ` Christoph Hellwig
2007-01-12 7:27 ` Benjamin Herrenschmidt
2007-01-11 11:25 ` [PATCH 3/7] Enable MSI on Powerpc Michael Ellerman
2007-01-11 21:37 ` Christoph Hellwig
2007-01-12 7:24 ` Benjamin Herrenschmidt
2007-01-11 11:25 ` [PATCH 5/7] MPIC MSI backend Michael Ellerman
2007-01-11 11:25 ` [PATCH 4/7] MPIC MSI allocator Michael Ellerman
2007-01-11 15:14 ` Segher Boessenkool
2007-01-11 17:19 ` Will Schmidt
2007-01-11 17:27 ` Segher Boessenkool
2007-01-12 0:27 ` Olof Johansson
2007-01-12 0:33 ` Michael Ellerman
2007-01-11 11:25 ` [PATCH 6/7] Enable MSI mappings for MPIC Michael Ellerman
2007-01-11 15:22 ` Segher Boessenkool [this message]
2007-01-11 11:25 ` [PATCH 7/7] Activate MSI for the MPIC backend on U3 Michael Ellerman
2007-01-11 15:23 ` [PATCH 0/7] Powerpc MSI Implementation Segher Boessenkool
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=b359a2c351f628252dc385285911d37e@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=olof@lixom.net \
--cc=paulus@samba.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).