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 D98E9C05027 for ; Fri, 17 Feb 2023 08:57:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229475AbjBQI55 (ORCPT ); Fri, 17 Feb 2023 03:57:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229966AbjBQI54 (ORCPT ); Fri, 17 Feb 2023 03:57:56 -0500 Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6008ABB89 for ; Fri, 17 Feb 2023 00:57:54 -0800 (PST) Received: by mail-ed1-x52a.google.com with SMTP id j20so3158839edw.0 for ; Fri, 17 Feb 2023 00:57:54 -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=JxmTPfEZSHv/qWrcZKvsN9uAVFNGcnCsPAcIEn+aGbM=; b=S3hhqXofYhKYklwyVx1ZiaQVV6VUVxQl+CNp6N2KHoO/UUbSNw+3Td5LP2oYASqzUE M7OAtXBpVInxsSayj23toB0vGa3eNd1R/CQzLMYehtOMXDEuBo+jRRWtYPdl3O3ymj68 wYm5hr3vcVph1ZKGwrTvEzyWyqWU+0sH66QfQFNQ5nNNs3PNdXWT6Mnsh0c/A065HGBh HRXIN+ARWXjVn2pAjZRKGW7pfCQNiJlAeyPy7XkwY8NKMPUL2xL+YDZWiQEw9m4eW24e Bp2IAnTkMM6ZShPMQdvPc31wCddIrMcKmJiEhEQDYvqTObdVIhFFUpBQ5bxu+X2sU97g bIkA== 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=JxmTPfEZSHv/qWrcZKvsN9uAVFNGcnCsPAcIEn+aGbM=; b=aUr8z39iFHzLe6EgcKagplR6jW1sl+9B6JZi1YfFHJAG32SB2ZsU7J3MT74Z6gpauq GNAEOGQkYkadZwS6F1ypwAESU4KrLTO85fvVWo05glW25QQcE9BLxoc9zR34AiPs/lmb seiC+gIbt0UVBKimsLJllmgC4B7Lu+3rK7c6UfUJfGw6oje8PU0A2WxBvhG90YV21l/N BlyJ6ayahi6xDy3u9/mt0qZNonMpouIcGMiZGVJ8NiZPd+QPqoiShN9PY3Hih4O9/Jk5 4Zra2u4OctsQjHAGZEHdmlPCaDwvwtjmDS2Fzp+epz8uzQIp8G5yi0ezGOXOIBq78ID5 ZAFQ== X-Gm-Message-State: AO0yUKUbb8MJafH3ZJjOAut+yI7qVjSWZTmPwIAbNecQ410ywHZchwKR Z7RmFTjxkJsCCRP6MNNJT863HQ== X-Google-Smtp-Source: AK7set9s6X9YCl0+Jv/Abcpk9KSI2ZLrpWThyt+bZQlD5CjypRTHefOM/EEsy2zJt587ycEEWaGNUQ== X-Received: by 2002:a17:906:944b:b0:8b1:3ba8:3f4d with SMTP id z11-20020a170906944b00b008b13ba83f4dmr8436182ejx.70.1676624272837; Fri, 17 Feb 2023 00:57:52 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id jz19-20020a17090775f300b008b17cc28d3dsm993330ejc.20.2023.02.17.00.57.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 17 Feb 2023 00:57:52 -0800 (PST) Message-ID: <6217b51c-4982-8548-688d-8bfce97d3352@linaro.org> Date: Fri, 17 Feb 2023 09:57:50 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH v10 05/10] dt-bindings: qcom-qce: Add new SoC compatible strings for Qualcomm QCE IP Content-Language: en-US To: Vladimir Zapolskiy , Krzysztof Kozlowski , Bjorn Andersson , Herbert Xu , Thara Gopinath , Bhupesh Sharma Cc: Rob Herring , Konrad Dybcio , Andy Gross , "David S. Miller" , devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org, Neil Armstrong References: <20230216131430.3107308-1-vladimir.zapolskiy@linaro.org> <20230216131430.3107308-6-vladimir.zapolskiy@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <20230216131430.3107308-6-vladimir.zapolskiy@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 16/02/2023 14:14, Vladimir Zapolskiy wrote: > Introduce a generic IP family compatible 'qcom,qce' and its two derivatives > based on SoC names rather than on IP versions. Having a generic compatible > is only partially sufficient, the QCE IP version can be discovered in > runtime, however there are two known groups of QCE IP versions, which > require different DT properties, these two groups are populated with SoC > based compatibles known at the moment. > > Keep the old compatibles 'qcom,crypto-v5.1' and 'qcom,crypto-v5.4' for > backward compatibility of DTB ABI, but mark them as deprecated. > As I asked at v9, please mention that you document already used v5.4 compatible. You do not "keep it", because it was never there in the binding. Best regards, Krzysztof