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 11EE8C636D4 for ; Thu, 9 Feb 2023 09:26:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230022AbjBIJ00 (ORCPT ); Thu, 9 Feb 2023 04:26:26 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33844 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229945AbjBIJ00 (ORCPT ); Thu, 9 Feb 2023 04:26:26 -0500 Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2C2DA18B3A for ; Thu, 9 Feb 2023 01:26:24 -0800 (PST) Received: by mail-wm1-x336.google.com with SMTP id k8-20020a05600c1c8800b003dc57ea0dfeso3422311wms.0 for ; Thu, 09 Feb 2023 01:26:24 -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=HdNCaQA/ISgeLU5P3fZ4D7O83T+ao8B3Lddz0QCvUKg=; b=dSjZgdi7QEnveCnZRK7wW3MF7Yivb43goIbFe2YhF9tExKUmw5Xr/YEe2+C7H8rJq1 LIe3hZJSrWhxh8djiBk69uJz08uNxQlKjPbo63HZmGK8e4Qfe0FJ1WvcsjVvPuTi8lLi mHWUcpR/pw/nSh5fGXNx7r3zgN/R/Z+ArIL0b08049Jx0lDFFh7fzEIV5yqKBG3pcpr1 ce5KhD0gsLwW1+NjFrjM7DEZDvO1NcBCtyzLSh9KVMLeN8PmJ3lbbJbinxKDfdcK84SU Yet8YNyCYE2mCRFCb7hZEKPc/AojaDOtXK7j1WLfT+oe58FbXF5CoX7kzTeNh+WcgFb8 AGNg== 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=HdNCaQA/ISgeLU5P3fZ4D7O83T+ao8B3Lddz0QCvUKg=; b=k9dGZBZHRQ2IONcfXJkp81VvDP5ssnmzWiUmoULTuaTHKYTCMwA7Gb2KLTPi5RwxJw FSZgnMANPUHnkFAarBubTRIyarAx2S/Cqu6qxGob//TDDkNlZ/EEH66/tfublV5+mFQq XFiBxuMAlZ2fddG4aJ8bJa1WbbW1j+a7Rs+dmqfh6pCWRM5Hcx4WjnufXJwBy0LA2PlW OmLkuF7Fkrwo4wwExlp9Eazo6W/Nm20/kk5xffoFZF/EsWG3MKPP+4k8fLMnYt/0OQsl akG2Q03I4k8NK1Y0DjdQt8yTz9z1BssGP0ZEIAvz+B+uRWKIQPXKyL2F3Amw4CrXcCBf 0KaQ== X-Gm-Message-State: AO0yUKU7MzNRx4sYU40MGeFErceasEf6Glb0DA8yIHXIoFMqM+Uj10z9 kL2ZPUn5FagYCOALgjhXtMtq2Q== X-Google-Smtp-Source: AK7set9215hWm4e1DkjEGdEPr1xhYcHwud0zS7JOIfssFkz9PA+uWdAidKNp2x5dBGXkXC4xZMjgdA== X-Received: by 2002:a05:600c:358b:b0:3df:9858:c02e with SMTP id p11-20020a05600c358b00b003df9858c02emr5320055wmq.3.1675934782803; Thu, 09 Feb 2023 01:26:22 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id f21-20020a05600c43d500b003dc522dd25esm1234234wmn.30.2023.02.09.01.26.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 09 Feb 2023 01:26:22 -0800 (PST) Message-ID: Date: Thu, 9 Feb 2023 10:26:20 +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 v9 14/14] crypto: qce: core: Add a compatible based on a SoC name 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 References: <20230208183755.2907771-1-vladimir.zapolskiy@linaro.org> <20230208183755.2907771-15-vladimir.zapolskiy@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <20230208183755.2907771-15-vladimir.zapolskiy@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 08/02/2023 19:37, Vladimir Zapolskiy wrote: > The added 'qcom,ipq4019-qce' and 'qcom,sm8150-qce' compatible values will > serve as QCE IP family compatibles, so that the crypto engine on added > platforms can derive from one of these two. Also the compatibles serve as > a fall-back for currently supported QCE IP variants on Qualcomm platforms. > > At the moment there is no need to differentiate or add any other SoC > specific compatible values to the list, however it's known in advance > that the two QCE IP families are not fully compatible between each other. > > The IP version based compatibles are left untouched to preserve backward > DTB ABI compatibility. Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof