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 A1865C46467 for ; Tue, 10 Jan 2023 10:12:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232324AbjAJKMO (ORCPT ); Tue, 10 Jan 2023 05:12:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39012 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232391AbjAJKL6 (ORCPT ); Tue, 10 Jan 2023 05:11:58 -0500 Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EA139544D4 for ; Tue, 10 Jan 2023 02:11:52 -0800 (PST) Received: by mail-wr1-x430.google.com with SMTP id j7so6155363wrn.9 for ; Tue, 10 Jan 2023 02:11:52 -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=jwoFAzmVct79bqJZEwpYCPbEy1KK9a8Xos32k6CB9ok=; b=rll1yyrS+IMjOPKuwpE7YSGZemxZTB6eFOYDpBF+hnLf8pmgI92TRe2Uyf6umZaBH2 dTewi4vtWoQvnsco1Y0GwBjco3YRBwE9eNJfS+spQmmdTIpaRZA8SQNDa8+Um6qcEI9n JzXiXLmKMuFZSvfxX+EUUFKYorZhohkXFIDMQGNmdgFsWGpqD+CbAqN6ibV0fM4yRPWo MdgnfslqwGcrq7rEOA9stDMeBRwZqR6nPqorJVQ3DGSsOiILzftPzHsGjPwAFPxBpBs0 zMdQwV8oK5cftcPpzfopRSmC+l/dsUZvzR523Ia7oFaRmtCUdOuEc9Udn9skxNgqDANr bvzg== 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=jwoFAzmVct79bqJZEwpYCPbEy1KK9a8Xos32k6CB9ok=; b=QOh7usCFa487BaR1eHZFtEo4cyDRDEaLUJGmNBRgVNhdYea3GB3n1/S/XWn0/tMtbw P9LK1SvyXZZB+SCARW+3aKH5ZdgQ55Xu95YsDHh2ZQSzE2GHmyN1imiI10CWSTaBE2r2 cjLqV5C7ZsA3S91we9B8db7B9YKzsH9P788rWPOwQ6oayBx07VBJFikE9PCmXVZ5cdR2 icMLbj5ZEkshd4wo+ZGkEUFJoAs7cMw3SWHChQys7oavJHxoRpzFO+Utiak21NZ9DrK1 7206+2VHzYa+aCEQJqe8VGbHRwLc1kKKnhxtd5zB0YiImy0AZhZ31u/9ASA6tlTJ1XNb R9gw== X-Gm-Message-State: AFqh2kpeasEUFQYL55cQc8VdKS61HgWhANPeufAgZ33f+6vntfgB39i4 +tIbzL82JbbaUqCKE9719hYngQ== X-Google-Smtp-Source: AMrXdXsZPpkq9cPmTR37ia51zvuv0bKJrlVZp8tgAuoG6eS7DKgEpCtJM1QJDTWTu2GwMRdxUu4i1A== X-Received: by 2002:adf:a3c9:0:b0:2b9:d6ba:21ef with SMTP id m9-20020adfa3c9000000b002b9d6ba21efmr13649879wrb.65.1673345511049; Tue, 10 Jan 2023 02:11:51 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id u24-20020adfa198000000b002bc84c55758sm2521030wru.63.2023.01.10.02.11.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Jan 2023 02:11:50 -0800 (PST) Message-ID: Date: Tue, 10 Jan 2023 11:11:48 +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 v4 3/3] dt-bindings: firmware: qcom: scm: Separate VMIDs from header to bindings Content-Language: en-US To: Konrad Dybcio , linux-arm-msm@vger.kernel.org, andersson@kernel.org, agross@kernel.org Cc: marijn.suijten@somainline.org, Rob Herring , Krzysztof Kozlowski , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, AngeloGioacchino Del Regno , Loic Poulain , Stephan Gerhold References: <20230109130523.298971-1-konrad.dybcio@linaro.org> <20230109130523.298971-3-konrad.dybcio@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <20230109130523.298971-3-konrad.dybcio@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On 09/01/2023 14:05, Konrad Dybcio wrote: > The SCM VMIDs represent predefined mappings that come from the > irreplaceable and non-omittable firmware that comes with every > Qualcomm SoC (unless you steal engineering samples from the factory) > and help clarify otherwise totally magic numbers which we are > required to pass to the secure world for some parts of the SoC to > work at all (with modem being the prime example). > > On top of that, with changes to the rmtfs binding, secure VMIDs will > become useful to have in device trees for readability. Separate them > out and add to include/dt-bindings. > > Signed-off-by: Konrad Dybcio > --- > v3 -> v4: Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof