From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f44.google.com ([209.85.208.44]:46382 "EHLO mail-ed1-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729536AbeHNPmu (ORCPT ); Tue, 14 Aug 2018 11:42:50 -0400 MIME-Version: 1.0 References: In-Reply-To: From: Ramon Fried Date: Tue, 14 Aug 2018 13:55:32 +0100 Message-ID: Subject: Re: PCI Endpoint - Missing inbound mapping ops ? To: kishon@ti.com Cc: 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: On Tue, Aug 14, 2018 at 1: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. Thanks Kishon. what about address mapping ? Synopsys has this functionality if I recall correctly. > > Thanks > Kishon