Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp1554147imp; Fri, 22 Feb 2019 06:03:22 -0800 (PST) X-Google-Smtp-Source: AHgI3IYGaa/c4H6DyabJ0cdGd3LjmdRVpDQRks97m7hQL9pLnb0H472yPf5ST6oQ4AelZqi21Msn X-Received: by 2002:a17:902:a508:: with SMTP id s8mr4166456plq.275.1550844202818; Fri, 22 Feb 2019 06:03:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550844202; cv=none; d=google.com; s=arc-20160816; b=gKO09B/6dmktNkbfVBUnd5dSL1t4GzuNA/EsIMaJSsRhGFmDbABMTO539G5zVnIP84 r3MW0xnxECkv+9drni89h5GMXUN//9i+wfMkLJQD3Hg1GJb8nk6OS8IXZvOCpNrg2EpQ 9h3YGtnFMaNmzJRnNDLaqGN0+uIzh72us97UF+lZiZS6I7IPIFMIhtNKNqUUnD+ANTWL HxTrz8qjbYj98VPoZTJsyCbp8LoZ/RcEbfcrSOJ49voatLTcaqbXttvZMerbTiJJQS/V UVayYfjcPszRtWS6vEXYBaCWgAB59L/8QbRsbdPrTj2yfDWYAueEkjLZQfk9HV9vUI3S 0nZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:thread-topic:subject:cc:to:from; bh=HfZcPCICGbjJ9e4bZCXvA/yl01ogeaPDi681ycDvD70=; b=07pKZz6khntrgzzCFN0INXGU8FehFaTkaLZeM7slyPO/KG3FYGd5zn2A+BxqTxM+5Y SBc3kACF72FKAtVIfA8BeAFZyE5DI49o+5Q45xDc0doMWwFJ1Mg46NQL3xDnNkIWArWS 2AUVKPyqeJ2JZEPKlQa4S28s7/n1G7nqgWTXLUjj1mDWUhOpMiGoey+IkVfkMIG4qS1q B/EcEr1Je/pMCUyeIFwyfMiziT1C7rR+waesT+ad45q60kxAHqt94i4QYIvWk6lgZ9rz ykQpruv3/uJ4AL1NaRwF9XUyBYxb6acoHIEPN1znoyw/FC2+TQis9fx82ZUtzn3hohnK Ts6Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j5si1415475plk.387.2019.02.22.06.03.06; Fri, 22 Feb 2019 06:03:22 -0800 (PST) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727024AbfBVOCh convert rfc822-to-8bit (ORCPT + 99 others); Fri, 22 Feb 2019 09:02:37 -0500 Received: from mx08-00178001.pphosted.com ([91.207.212.93]:56359 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726090AbfBVOCh (ORCPT ); Fri, 22 Feb 2019 09:02:37 -0500 Received: from pps.filterd (m0046661.ppops.net [127.0.0.1]) by mx08-00178001.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x1ME1wJ6000795; Fri, 22 Feb 2019 15:02:24 +0100 Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx08-00178001.pphosted.com with ESMTP id 2qpc75k1tv-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 22 Feb 2019 15:02:24 +0100 Received: from zeta.dmz-eu.st.com (zeta.dmz-eu.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id B372138; Fri, 22 Feb 2019 14:02:20 +0000 (GMT) Received: from Webmail-eu.st.com (sfhdag7node3.st.com [10.75.127.21]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id C911B5348; Fri, 22 Feb 2019 14:02:20 +0000 (GMT) Received: from SFHDAG7NODE2.st.com (10.75.127.20) by SFHDAG7NODE3.st.com (10.75.127.21) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Fri, 22 Feb 2019 15:02:20 +0100 Received: from SFHDAG7NODE2.st.com ([fe80::d548:6a8f:2ca4:2090]) by SFHDAG7NODE2.st.com ([fe80::d548:6a8f:2ca4:2090%20]) with mapi id 15.00.1347.000; Fri, 22 Feb 2019 15:02:20 +0100 From: Loic PALLARDY To: Christoph Hellwig , Stephen Rothwell CC: Bjorn Andersson , Linux Next Mailing List , Linux Kernel Mailing List Subject: RE: linux-next: build failure after merge of the rpmsg tree Thread-Topic: linux-next: build failure after merge of the rpmsg tree Thread-Index: AQHUym4KrK9haDF6O0m4TBapWT3oEKXrtNUAgAAks1A= Date: Fri, 22 Feb 2019 14:02:20 +0000 Message-ID: References: <20190222161817.32e35462@canb.auug.org.au> <20190222125046.GB29125@lst.de> In-Reply-To: <20190222125046.GB29125@lst.de> Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.75.127.50] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-02-22_10:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Changes in remoteproc have been introduced to associate dedicated dma coherent memory pool to each virtio device. It is needed when we have several virtio devices for which buffers can't be allocated from the same memory region. Patch introduces support in both ways: - memory region declared thanks to reserved memory and associated thanks to of_reserved_mem_device_init_by_idx(): mainly used for regions located in DDR. - memory region specified in rproc driver itself and defined as dma coherent thanks to dma_declare_coherent_memory(): These regions are generally located in coprocessor/SoC internal memories and declared in different ways by the different rproc drivers (regs in DT, hard coded values in drivers...). For me, dma_declare_coherent_memory based solution is there to allow a smooth transition from current rproc drivers implementations to a cleaner and unified one based on reserved memory declaration. Regards, Loic > -----Original Message----- > From: Christoph Hellwig > Sent: vendredi 22 f?vrier 2019 13:51 > To: Stephen Rothwell > Cc: Bjorn Andersson ; Christoph Hellwig > ; Linux Next Mailing List ; Linux > Kernel Mailing List ; Loic PALLARDY > > Subject: Re: linux-next: build failure after merge of the rpmsg tree > > FYI, can I please get an explanation for the remoteproc changes? > > We really should avoid adding new callers of > dma_declare_coherent_memory, > which is a rather badly designed interface.