From mboxrd@z Thu Jan 1 00:00:00 1970 From: hanjun.guo@linaro.org (Hanjun Guo) Date: Wed, 30 Nov 2016 11:22:42 +0800 Subject: [PATCH v9 15/16] drivers: acpi: iort: add single mapping function In-Reply-To: <20161121100148.24769-16-lorenzo.pieralisi@arm.com> References: <20161121100148.24769-1-lorenzo.pieralisi@arm.com> <20161121100148.24769-16-lorenzo.pieralisi@arm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 2016/11/21 18:01, Lorenzo Pieralisi wrote: > The current IORT id mapping API requires components to provide > an input requester ID (a Bus-Device-Function (BDF) identifier for > PCI devices) to translate an input identifier to an output > identifier through an IORT range mapping. > > Named components do not have an identifiable source ID therefore > their respective input/output mapping can only be defined in > IORT tables through single mappings, that provide a translation > that does not require any input identifier. > > Current IORT interface for requester id mappings (iort_node_map_rid()) > is not suitable for components that do not provide a requester id, > so it cannot be used for IORT named components. > > Add an interface to the IORT API to enable retrieval of id > by allowing an indexed walk of the single mappings array for > a given component, therefore completing the IORT mapping API. > > Signed-off-by: Lorenzo Pieralisi > Reviewed-by: Tomasz Nowicki > Tested-by: Hanjun Guo > Tested-by: Tomasz Nowicki > Cc: Hanjun Guo > Cc: Tomasz Nowicki > Cc: "Rafael J. Wysocki" > --- > drivers/acpi/arm64/iort.c | 39 +++++++++++++++++++++++++++++++++++++++ > 1 file changed, 39 insertions(+) Acked-by: Hanjun Guo Thanks Hanjun