Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Yash Shah <yash.shah@sifive.com>
To:     "Paul Walmsley ( Sifive)" <paul.walmsley@sifive.com>
CC:     "Paul Walmsley ( Sifive)" <paul.walmsley@sifive.com>,
        "Palmer Dabbelt ( Sifive)" <palmer@sifive.com>,
        "linux-riscv@lists.infradead.org" <linux-riscv@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
        "will@kernel.org" <will@kernel.org>,
        "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
        "allison@lohutok.net" <allison@lohutok.net>,
        "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
        "tglx@linutronix.de" <tglx@linutronix.de>,
        "Anup.Patel@wdc.com" <Anup.Patel@wdc.com>,
        "rppt@linux.ibm.com" <rppt@linux.ibm.com>,
        Greentime Hu <greentime.hu@sifive.com>,
        "alex@ghiti.fr" <alex@ghiti.fr>,
        "logang@deltatee.com" <logang@deltatee.com>,
        "sorear2@gmail.com" <sorear2@gmail.com>,
        Sachin Ghadi <sachin.ghadi@sifive.com>
Subject: RE: [PATCH v2] RISC-V: Add PCIe I/O BAR memory mapping
Thread-Topic: [PATCH v2] RISC-V: Add PCIe I/O BAR memory mapping
Thread-Index: AQHViw5l0jY9JQhUEkq6xffYZOywOadrgoeAgAWHKLA=
Date:   Tue, 29 Oct 2019 04:19:56 +0000
Message-ID: <CH2PR13MB3368A6E99DAB164A52D2954A8C610@CH2PR13MB3368.namprd13.prod.outlook.com>
References: <1571992163-6811-1-git-send-email-yash.shah@sifive.com>
 <alpine.DEB.2.21.9999.1910250852420.28076@viisi.sifive.com>
In-Reply-To: <alpine.DEB.2.21.9999.1910250852420.28076@viisi.sifive.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: sifive.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a71613c0-7ad6-41ea-c404-08d75c274136
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Oct 2019 04:19:56.3003
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 22f88e9d-ae0d-4ed9-b984-cdc9be1529f1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 7dPlHCLmbI+c1hn/2tr4Q6S9mfcTqpwbYBTNN+JttOH6YMxcxRlmlKP++uzFUIkVSXBJL+5FyOtkh9VPuGDH1Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR13MB3445
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> On Fri, 25 Oct 2019, Yash Shah wrote:
>=20
> > For legacy I/O BARs (non-MMIO BARs) to work correctly on RISC-V Linux,
> > we need to establish a reserved memory region for them, so that
> > drivers that wish to use the legacy I/O BARs can issue reads and
> > writes against a memory region that is mapped to the host PCIe
> > controller's I/O BAR mapping.
> >
> > Signed-off-by: Yash Shah <yash.shah@sifive.com>
>=20
> Thanks.  And just to confirm: this is a fix, right?  Without this patch, =
legacy
> PCIe I/O resources won't be accessible on RISC-V?

Yes, this is a fix.

- Yash