From: Bjorn Helgaas <bhelgaas@google.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v3 5/5] PCI: designware: set up high part of MSI target address
Date: Sat, 15 Aug 2015 11:16:08 -0500 [thread overview]
Message-ID: <20150815161608.GI26431@google.com> (raw)
In-Reply-To: <1439475392.13210.19.camel@pengutronix.de>
On Thu, Aug 13, 2015 at 04:16:32PM +0200, Lucas Stach wrote:
> Hi Bjorn,
>
> I'm going to respin this patch to fix it regarding Pratyushs comment.
>
> In such a situation do you prefer a repost of the whole series or rather
> just have the single fixed patch reposted?
The easiest thing for me is a new v4 series. It's easy for me to
make a mistake when assembling from pieces.
> Am Mittwoch, den 12.08.2015, 21:05 +0530 schrieb Pratyush Anand:
> > On Wed, Aug 12, 2015 at 3:03 PM, Lucas Stach <l.stach@pengutronix.de> wrote:
> > > Set up the high part of the MSI target address in order to allow the
> > > MSI target to reside above the 4GB mark on 64bit and PAE systems.
> > >
> > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > > ---
> > > drivers/pci/host/pcie-designware.c | 9 ++++++---
> > > 1 file changed, 6 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/pci/host/pcie-designware.c b/drivers/pci/host/pcie-designware.c
> > > index 74034395cf2a..fcb798e47c30 100644
> > > --- a/drivers/pci/host/pcie-designware.c
> > > +++ b/drivers/pci/host/pcie-designware.c
> > > @@ -299,12 +299,15 @@ no_valid_irq:
> > > static void dw_msi_setup_msg(struct pcie_port *pp, unsigned int irq, u32 pos)
> > > {
> > > struct msi_msg msg;
> > > + u64 msi_target;
> > >
> > > if (pp->ops->get_msi_addr)
> > > - msg.address_lo = pp->ops->get_msi_addr(pp);
> > > + msi_target = pp->ops->get_msi_addr(pp);
> > > else
> > > - msg.address_lo = virt_to_phys((void *)pp->msi_data);
> > > - msg.address_hi = 0x0;
> > > + msi_target = virt_to_phys((void *)pp->msi_data);
> > > +
> > > + msg.address_lo = (u32)(msi_target & 0xffffffff);
> > > + msg.address_hi = (u32)(msi_target >> 32 & 0xffffffff);
> > >
> > > if (pp->ops->get_msi_data)
> > > msg.data = pp->ops->get_msi_data(pp, pos);
> >
> > Other than above, dw_pcie_msi_init also need to be fixed
> > for PCIE_MSI_ADDR_HI.
>
> --
> Pengutronix e.K. | Lucas Stach |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
>
prev parent reply other threads:[~2015-08-15 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:33 [PATCH v3 0/5] Designware host multivector MSI and 64bit MSI fixes Lucas Stach
2015-08-12 9:33 ` [PATCH v3 1/5] PCI: allow MSI chip providers to implement their own multivector MSI setup Lucas Stach
2015-08-12 14:57 ` Pratyush Anand
2015-08-12 9:33 ` [PATCH v3 2/5] PCI: designware: factor out MSI msg setup Lucas Stach
2015-08-12 15:09 ` Pratyush Anand
2015-08-12 9:33 ` [PATCH v3 3/5] PCI: designware: implement multivector MSI irq setup Lucas Stach
2015-08-12 15:11 ` Pratyush Anand
2015-08-12 9:33 ` [PATCH v3 4/5] PCI: designware: change prototype of get_msi_addr Lucas Stach
2015-08-12 15:13 ` Pratyush Anand
2015-08-12 9:33 ` [PATCH v3 5/5] PCI: designware: set up high part of MSI target address Lucas Stach
2015-08-12 15:35 ` Pratyush Anand
2015-08-13 14:16 ` Lucas Stach
2015-08-15 16:16 ` Bjorn Helgaas [this message]
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=20150815161608.GI26431@google.com \
--to=bhelgaas@google.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.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).