From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f177.google.com ([209.85.216.177]:33130 "EHLO mail-qt0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729955AbeHNPz2 (ORCPT ); Tue, 14 Aug 2018 11:55:28 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Miguel Ojeda Date: Tue, 14 Aug 2018 15:08:00 +0200 Message-ID: Subject: Re: PCI Endpoint - Missing inbound mapping ops ? To: Kishon Vijay Abraham I Cc: Ramon Fried , lorenzo.pieralisi@arm.com, bhelgaas@google.com, linux-pci@vger.kernel.org, open list Content-Type: text/plain; charset="UTF-8" Sender: linux-pci-owner@vger.kernel.org List-ID: Hi Kishon, On Tue, Aug 14, 2018 at 2:53 PM, Kishon Vijay Abraham I wrote: > Hi, > > On Tuesday 14 August 2018 06:19 PM, Ramon Fried wrote: >> Hi. >> I recently saw that the PCI endpoint API only supports outbound memory >> mapping: (AXI -> PCI) through the map_addr op. >> Why inbound mapping is missing (PCI->AXI) is missing ? >> In almost all of the PCI EP controllers I've worked with there was a >> need to map complete BARS or part of BARS to mmio/aperature regions on >> the device. > > pci_epc_set_bar() is used for mapping BAR. Just to let you know, the ARC/DKIM seems wrong according to gmail and is marked as spam. It seems it happens from time to time. Bjorn Helgaas (in CC) also had the same problem a couple of years ago. Cheers, Miguel > > Thanks > Kishon