linux-kernel - Re: [PATCH v9] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL PCIe Host Controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Nov 2015 09:56:14 +0000
From:	Marc Zyngier <marc.zyngier@....com>
To:	Amit Tomer <amittomer25@...il.com>
Cc:	Bharat Kumar Gogada <bharat.kumar.gogada@...inx.com>,
	"mark.rutland@....com" <mark.rutland@....com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"tinamdar@....com" <tinamdar@....com>,
	"pawel.moll@....com" <pawel.moll@....com>,
	"m-karicheri2@...com" <m-karicheri2@...com>,
	Michal Simek <michals@...inx.com>,
	"rjui@...adcom.com" <rjui@...adcom.com>,
	"treding@...dia.com" <treding@...dia.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"arnd@...db.de" <arnd@...db.de>,
	"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
	"hauke@...ke-m.de" <hauke@...ke-m.de>,
	"robh+dt@...nel.org" <robh+dt@...nel.org>,
	Ravikiran Gummaluri <rgummal@...inx.com>,
	"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"sbranden@...adcom.com" <sbranden@...adcom.com>,
	"dhdang@....com" <dhdang@....com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Minghuan.Lian@...escale.com" <Minghuan.Lian@...escale.com>,
	Soren Brinkmann <sorenb@...inx.com>,
	"galak@...eaurora.org" <galak@...eaurora.org>
Subject: Re: [PATCH v9] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL
 PCIe Host Controller

On Wed, 25 Nov 2015 14:23:29 +0530
Amit Tomer <amittomer25@...il.com> wrote:

> Sorry to intervene but just trying to learn from your comments.
> 
>  > You have plenty, and that's the whole of your device space. *All of it*. So
> >   just take the base address of your PCIe controller, and be done with
> >   it.
> 
> but isn't few of PCIe controller's registers itself are mapped
> here(base address). So, how can we use this address for MSI?

You can, because the PCIe controller never writes to itself. If it
writes to that base address, then it *is* the MSI doorbell and the
bridge will hopefully do the right thing.

> Or you said from base address of PCIe controller, find an offset that
> can be used as MSI address?

That works as well. Given the description of the HW we've been given,
any address will do, as long as it is behind the PCIe RC.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/