public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: valmiki <valmikibow@gmail.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Cc: helgaas@kernel.org, arnd@arndb.de, mark.rutland@arm.com
Subject: Re: Need clarity on MSI handling in RC driver
Date: Wed, 4 Jan 2017 17:46:19 +0000	[thread overview]
Message-ID: <060e94a4-00a2-bdb7-caf3-72785b333c83@arm.com> (raw)
In-Reply-To: <307e8512-7e14-39a2-c225-6db44e443aea@gmail.com>

On 04/01/17 17:39, valmiki wrote:
> Hi All,
> 
> I have a doubt, the MSI domains are handled differently in different RC 
> drivers.
> 
> Some drivers use irq_domain_add_linear alone, and some use 
> pci_msi_create_irq_domain also to handle MSI.
> 
> In most of the 32-bit architectures only irq_domain_add_linear is used 
> and in 64 bit drivers both pci_msi_create_irq_domain and 
> irq_domain_add_linear are used.
> 
> So is this because of architecture difference between ARM and ARM64 ?

Neither. This is purely a software construct. Newer drivers use the
generic MSI infrastructure (which also allows things like non-PCI MSI),
while older drivers use some ad-hoc infrastructure which is more or less
specific to PCI.

The former is the way to go, and the latter is being phased out.

I'll let Mark draw some shiny ASCII art.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2017-01-04 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  3:17 Need clarity on PCIe MSI interrupt in device tree valmiki
2017-01-04  8:29 ` Marc Zyngier
2017-01-04 17:28   ` valmiki
2017-01-04 10:05 ` Mark Rutland
2017-01-04 17:29   ` valmiki
2017-01-04 17:39 ` Need clarity on MSI handling in RC driver valmiki
2017-01-04 17:46   ` Marc Zyngier [this message]
2017-01-06  2:30     ` valmiki

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=060e94a4-00a2-bdb7-caf3-72785b333c83@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=arnd@arndb.de \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=valmikibow@gmail.com \
    /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