All of lore.kernel.org
 help / color / mirror / Atom feed
From: bharatku@xilinx.com (Bharat)
To: linux-arm-kernel@lists.infradead.org
Subject: PCIe MSI address is not written at pci_enable_msi_range call
Date: Mon, 11 Jul 2016 05:55:09 +0000 (UTC)	[thread overview]
Message-ID: <loom.20160711T075401-257@post.gmane.org> (raw)

Hi, 

I have a query.
I see that when we use PCI_MSI_IRQ_DOMAIN to handle MSI's, MSI address is
not being written in to end point's PCI_MSI_ADDRESS_LO/HI at the call
pci_enable_msi_range.

Instead it is being written at the time end point requests irq.

Can any one tell the reason why is it handled in this manner ?

Correct me If my observation is wrong.

Thanks & Regards,
Bharat

             reply	other threads:[~2016-07-11  5:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11  5:55 Bharat [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-11  2:37 PCIe MSI address is not written at pci_enable_msi_range call Bharat Kumar Gogada
2016-07-11  2:32 Bharat Kumar Gogada
2016-07-11  8:47 ` Marc Zyngier
2016-07-11  9:33   ` Bharat Kumar Gogada
2016-07-11 10:21     ` Marc Zyngier
2016-07-11 10:51       ` Bharat Kumar Gogada
2016-07-11 15:50         ` Marc Zyngier
2016-07-12  9:11           ` Bharat Kumar Gogada
2016-07-12 14:28             ` Marc Zyngier
2016-07-12 15:56     ` Marc Zyngier
2016-07-13  6:22       ` Bharat Kumar Gogada
2016-07-13  8:16         ` Marc Zyngier
2016-07-13  8:33           ` Bharat Kumar Gogada
2016-07-13  8:37             ` Marc Zyngier
2016-07-13  9:10               ` Bharat Kumar Gogada
2016-07-13  9:19                 ` Marc Zyngier
2016-07-13  9:36                   ` Bharat Kumar Gogada
2016-07-13  9:40                     ` Marc Zyngier
2016-07-13 15:34                       ` Bharat Kumar Gogada
2016-07-13 15:39                         ` Marc Zyngier
2016-07-20 12:19             ` Marc Zyngier
2016-07-27 11:14               ` Bharat Kumar Gogada

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=loom.20160711T075401-257@post.gmane.org \
    --to=bharatku@xilinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.