From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D36BDC6FD1C for ; Tue, 14 Mar 2023 09:42:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229810AbjCNJmd (ORCPT ); Tue, 14 Mar 2023 05:42:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41208 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231124AbjCNJm0 (ORCPT ); Tue, 14 Mar 2023 05:42:26 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [46.235.227.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0899C6F61A; Tue, 14 Mar 2023 02:42:21 -0700 (PDT) Received: from [192.168.1.100] (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id E570D660308B; Tue, 14 Mar 2023 09:42:19 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1678786940; bh=GSNV5roZLwwl6G8WfQf2/I4I3R94zmwTu0GyKcNinaE=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=MioD6rmPfCWH4SyemOidFwpl6xpI4xyRC1tLnJBk6ngg2AOUaiPjO/rJwnZ5yIBbj UN2ZkX4cGQp+uffRpwr/exVEPpL+AFmzDfRPXBTLWNMwMbKwRH6IfFUuj2g6Ok6TH5 0pNV5SGExtnmv1P0VGkUPtPXEe7u9EFiNUn5PHWRdsrjrJWURxCxREhgOPI8Uvbfkb 7SD0n6kiy/I7pKiW99riflHcLGItgtRky99Vez0d/B0cPUrPJHhNKeU/unDwI383Xq hkC4/jThrASXHVig2xCMzV4+LZLOh+LESvq7cFURDfwpLuFzquS+m9rI9WPKJcvtHm tQVIViuyp+ErQ== Message-ID: <691cc1fd-7c49-841d-5424-f268fd7cba3b@collabora.com> Date: Tue, 14 Mar 2023 10:42:17 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v8 06/11] remoteproc: mediatek: Probe multi-core SCP Content-Language: en-US To: Tinghan Shen , Bjorn Andersson , Mathieu Poirier , Rob Herring , Krzysztof Kozlowski , Matthias Brugger Cc: linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Project_Global_Chrome_Upstream_Group@mediatek.com References: <20230303083355.3378-1-tinghan.shen@mediatek.com> <20230303083355.3378-7-tinghan.shen@mediatek.com> From: AngeloGioacchino Del Regno In-Reply-To: <20230303083355.3378-7-tinghan.shen@mediatek.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-remoteproc@vger.kernel.org Il 03/03/23 09:33, Tinghan Shen ha scritto: > The difference of single-core SCP and multi-core SCP device tree is > the presence of child device nodes described SCP cores. The SCP > driver populates the platform device and checks the child nodes > to identify whether it's a single-core SCP or a multi-core SCP. > > The resource structure of the multi-core SCP is a list of remoteproc > instances which is different to the single-core SCP. The corresponding > resource releasing action is based on the type of SCP. > > Signed-off-by: Tinghan Shen Reviewed-by: AngeloGioacchino Del Regno