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 95D87C46467 for ; Sat, 7 Jan 2023 10:43:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230299AbjAGKnD (ORCPT ); Sat, 7 Jan 2023 05:43:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44774 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236839AbjAGKmx (ORCPT ); Sat, 7 Jan 2023 05:42:53 -0500 Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9F32FEBC for ; Sat, 7 Jan 2023 02:42:50 -0800 (PST) Received: by mail-lf1-x12a.google.com with SMTP id m6so5507654lfj.11 for ; Sat, 07 Jan 2023 02:42:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=kGN16aqYn7nnEFzLqCDtMXfMmc5KaVn18pKv+2l0zPs=; b=VY6oNvkmWjhRGic3GpIAfMU1yEMK3tGNHwnDzV6wHrhp4Fbe0g3dAEcc9NRFRQseSh ZiXkGIpNBi7jMJVNVqJ5Di9K2HNXRajJFPm9WNpbonRZhzJ2m5Sevy5n7EIbo/14Jc33 67tISzYCv6Jrrjnjk9e72nOwg45IaCKlU8LwTRpvNtBS/VoIHXgR2EjIURaao6Co7suX y94J3fb1pvMglACkQGj4mUjhJz5TR4YoES4lmvxEqZKPAyqBAc84wkvIumBUAr4ddLgr yXFAyC9exRV2N2DuV9s2UK6JV0V0Uhy55fddnnQU3RSbUXcmfU/+XWiVOeN5zuiUvO6R QePw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=kGN16aqYn7nnEFzLqCDtMXfMmc5KaVn18pKv+2l0zPs=; b=ByKqsXKnJG0AVWrsVFvYfPWpmfn5LYHeVtV/qRrCKDKcCN6JDyIWBTx2OC2/W2o2Wu lfV/bl0CxGYh48AwMDV6lV6oBbh5F4m0/4IjEkZTHiIPLW06aVl/U8zXoIet6CHIWmFG ytVrgQckdCHTa1A7AnDEr+taHZ2LlE8OJjaJRKGgnxR7oCNQsUb7bnkruklWpTptzrEW O3s2jNlGGg3YIs6m5IYqshvibnz/BbRh7Q0CmhUpXhlvDaMSYeNJ80f8cUI1VYJou0RM FLUuMAOFd8RYmSImjYHa8PdgozCu3gdnPloV/ZT7YzocvXcrtEXkKwk8sQQ6fPX0HMH3 YLtA== X-Gm-Message-State: AFqh2kpBWlkKJbQZmxKKDAzBrh1z2EuGg0oRBvpKkpQZl/AkBrgi7ENi Gi0OnRvBIVo/HIhHk0LdPzEOVg== X-Google-Smtp-Source: AMrXdXvCBCR/iCDguU7sLHfJxkX+3TX2Kf/NNCLnyW6RQirRqdHF7YJwwhhzcrCpPLB2CmMni/Nn9Q== X-Received: by 2002:a05:6512:2987:b0:4a4:68b7:d642 with SMTP id du7-20020a056512298700b004a468b7d642mr16526215lfb.41.1673088169031; Sat, 07 Jan 2023 02:42:49 -0800 (PST) Received: from [192.168.1.101] (abxi45.neoplus.adsl.tpnet.pl. [83.9.2.45]) by smtp.gmail.com with ESMTPSA id m17-20020a056512015100b004cb45148027sm529467lfo.203.2023.01.07.02.42.48 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 07 Jan 2023 02:42:48 -0800 (PST) Message-ID: Date: Sat, 7 Jan 2023 11:42:47 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v2 1/2] dt-bindings: reserved-memory: rmtfs: Document qcom,assign-to-nav Content-Language: en-US To: Bjorn Andersson Cc: linux-arm-msm@vger.kernel.org, agross@kernel.org, krzysztof.kozlowski@linaro.org, marijn.suijten@somainline.org, Rob Herring , Krzysztof Kozlowski , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230102165034.830620-1-konrad.dybcio@linaro.org> <20230106175558.7sfutxaishdlwhoe@builder.lan> From: Konrad Dybcio In-Reply-To: <20230106175558.7sfutxaishdlwhoe@builder.lan> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6.01.2023 18:55, Bjorn Andersson wrote: > On Mon, Jan 02, 2023 at 05:50:33PM +0100, Konrad Dybcio wrote: >> Some SoCs mandate that the RMTFS is also assigned to the NAV VM, while >> others really don't want that. Since it has to be conditional, add a >> bool property to toggle this behavior. >> >> Signed-off-by: Konrad Dybcio >> --- >> v1 -> v2: >> - Rewrite the newly added description >> >> .../devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml b/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml >> index 2998f1c8f0db..4026788a4e40 100644 >> --- a/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml >> +++ b/Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml >> @@ -31,6 +31,12 @@ properties: >> description: > >> vmid of the remote processor, to set up memory protection >> >> + qcom,assign-to-nav: >> + type: boolean >> + description: >> + Whether to also assign the region to a third (NAV) VM, as opposed to >> + the usual 2. > > For better or worse, the binding currently takes the vmid of the first > instance in qcom,vmid. Would it not be cleaner to turn qcom,vmid into an > array and pass the nav vmid as a second element in that array? I suppose I could do that.. Konrad > > Regards, > Bjorn > >> + >> required: >> - qcom,client-id >> >> -- >> 2.39.0 >>