From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Loic Pallardy Subject: [PATCH 0/2] Remoteproc: Add predefined coprocessor memory mapping support Date: Fri, 26 Aug 2016 22:19:53 +0200 Message-ID: <1472242795-23970-1-git-send-email-loic.pallardy@st.com> MIME-Version: 1.0 Content-Type: text/plain To: bjorn.andersson@linaro.org, ohad@wizery.com, lee.jones@linaro.org Cc: loic.pallardy@st.com, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org List-ID: Hi all, Due to diverse constraints like SoC design, coprocessor characteristics, security context, etc, coprocessor memory mapping may be predefined/fixed at system level. In that case remoteproc should respect the different memory regions allocated to coprocessor in order to ensure proper operations. The following patches implement support of fixed memory region predefined in firmware resource table. During resource table handling, if resource physical address is defined, i.e different from 0x0 or 0xFFFFFFFF (-1), remoteproc enables memory region access using memremap function. If resource physical address is not defined, current behavior is preserved. Best regards, Loic Loic Pallardy (2): remoteproc: Modify FW_RSC_ADDR_ANY definition remoteproc: core: Add fixed memory region support drivers/remoteproc/remoteproc_core.c | 61 ++++++++++++++++++++++++++---------- include/linux/remoteproc.h | 6 +++- 2 files changed, 50 insertions(+), 17 deletions(-) -- 1.9.1 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754383AbcHZVsj (ORCPT ); Fri, 26 Aug 2016 17:48:39 -0400 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:37395 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754304AbcHZVsi (ORCPT ); Fri, 26 Aug 2016 17:48:38 -0400 From: Loic Pallardy To: , , CC: , , Subject: [PATCH 0/2] Remoteproc: Add predefined coprocessor memory mapping support Date: Fri, 26 Aug 2016 22:19:53 +0200 Message-ID: <1472242795-23970-1-git-send-email-loic.pallardy@st.com> X-Mailer: git-send-email 1.9.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.129.7.211] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-08-26_14:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, Due to diverse constraints like SoC design, coprocessor characteristics, security context, etc, coprocessor memory mapping may be predefined/fixed at system level. In that case remoteproc should respect the different memory regions allocated to coprocessor in order to ensure proper operations. The following patches implement support of fixed memory region predefined in firmware resource table. During resource table handling, if resource physical address is defined, i.e different from 0x0 or 0xFFFFFFFF (-1), remoteproc enables memory region access using memremap function. If resource physical address is not defined, current behavior is preserved. Best regards, Loic Loic Pallardy (2): remoteproc: Modify FW_RSC_ADDR_ANY definition remoteproc: core: Add fixed memory region support drivers/remoteproc/remoteproc_core.c | 61 ++++++++++++++++++++++++++---------- include/linux/remoteproc.h | 6 +++- 2 files changed, 50 insertions(+), 17 deletions(-) -- 1.9.1