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 EA6AAC64EC4 for ; Fri, 10 Mar 2023 08:14:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230200AbjCJIOF (ORCPT ); Fri, 10 Mar 2023 03:14:05 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59516 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230197AbjCJINe (ORCPT ); Fri, 10 Mar 2023 03:13:34 -0500 Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7D0D7527B for ; Fri, 10 Mar 2023 00:13:32 -0800 (PST) Received: by mail-ed1-x533.google.com with SMTP id s11so17151601edy.8 for ; Fri, 10 Mar 2023 00:13:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678436011; 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=CEPOx6Kwho4WulB2OeUMcq60ngC+gDTko4FaO6LvQts=; b=fZO54m22EllMgQT3ljYOGeNEoUes1cH0hDHzecRdbywedL6XngZKkw1h0xFv5H2mXA 0DmmTjVjV1k2ehBU0S7hULfTJSgfWiC+Qp04O5rGgtLWrVRypNIQLaHsSDSzhpJsy+6i eguZ/PtTKqp5Fu+Q6JCmNdU89nnvScLgXI3PX4QC5mysGM4nNQYX5f2oosbNNgwT9K+E b4x6HJqkIrRjTBnnQd2OBSwOGeehXml3thjck3Ty6gVMcOoVfFw0lKSJf/Dx6AjWRKfH Pvi146UrueYcO2IlPyuaTpspwHX4zKV256ZNAyoyKe+7xi4UEeTUsENpz0WkT6U6l6NV fjzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678436011; 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=CEPOx6Kwho4WulB2OeUMcq60ngC+gDTko4FaO6LvQts=; b=KO9XHt2X37sLFe9ivYfaWETV5gOVPVEo/5Foubv7V0VTJaaP1zclWAXd5F2lmWk09z uF/fkdgX/bC9GehH+OABbH2HQDrOTRiCfkeo4Y4aLbJlOv3tqp4k5I54dzXyoZIGcPfV +iAz2gFOvtKMM50WnD5gtVE0r0xi4xbXi2sdUA/7Fz8GZkjQDLfssawyTPS/KoXgi4qS Zxsb9re4LWPnmh0T3PYz0I1VhF3ZQlz/p4B2JyNioERMRb+j/+GsqXcnRVV2StQaMBbp TuxW4wJpVjqe54g6L2FdRuDJkfjLqPcjZ6A6C0Nyx4PH4pr9KfjFRou04biM1cNjgq95 JBPQ== X-Gm-Message-State: AO0yUKWFbKL9OBxS4saj12xLF/Jy5zf+XGpCLJOSqcFtfRW9MUi8ll3D +rfwgexSx6cosdB+oihc4MCzbw== X-Google-Smtp-Source: AK7set8hHmBQYQjiev7icT060MuM2aDe1d5sXieWR847rpHIWIaqa2m9i4Cs+I/TgT7t42q1surT2g== X-Received: by 2002:a05:6402:7ce:b0:4c0:57b:47a9 with SMTP id u14-20020a05640207ce00b004c0057b47a9mr21919985edy.35.1678436010973; Fri, 10 Mar 2023 00:13:30 -0800 (PST) Received: from ?IPV6:2a02:810d:15c0:828:2a59:841a:ebc:7974? ([2a02:810d:15c0:828:2a59:841a:ebc:7974]) by smtp.gmail.com with ESMTPSA id c22-20020a50d656000000b004c09527d62dsm525188edj.30.2023.03.10.00.13.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Mar 2023 00:13:30 -0800 (PST) Message-ID: Date: Fri, 10 Mar 2023 09:13:29 +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: [RFC PATCH v2 7/7] arm64: dts: qcom: Add the Inline Crypto Engine nodes Content-Language: en-US To: Eric Biggers Cc: Abel Vesa , Ulf Hansson , Rob Herring , Krzysztof Kozlowski , Andy Gross , Bjorn Andersson , Konrad Dybcio , Manivannan Sadhasivam , Alim Akhtar , Avri Altman , Bart Van Assche , Adrian Hunter , "James E . J . Bottomley" , "Martin K . Petersen" , linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, Linux Kernel Mailing List , linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org References: <20230308155838.1094920-1-abel.vesa@linaro.org> <20230308155838.1094920-8-abel.vesa@linaro.org> <4eab53fc-2d26-dc93-3ae6-c0b2546ad3e0@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 09/03/2023 19:31, Eric Biggers wrote: > On Thu, Mar 09, 2023 at 11:31:46AM +0100, Krzysztof Kozlowski wrote: >> On 08/03/2023 16:58, Abel Vesa wrote: >>> Drop all properties related to ICE from every UFS and SDCC node, >>> for all platforms, and add dedicated ICE nodes for each platform. >>> On most platforms, there is only one ICE instance, used by either >>> UFS or SDCC, but there are some platforms that have two separate >>> instances and, therefore, two separate nodes are added. >>> >>> Signed-off-by: Abel Vesa >>> --- >>> >>> Changes since v1: >>> * Made changes for all platforms that use ICE, as a single patch since >>> most changes look really similar. >>> >>> arch/arm64/boot/dts/qcom/sdm630.dtsi | 18 +++++++++----- >>> arch/arm64/boot/dts/qcom/sdm670.dtsi | 15 +++++++---- >>> arch/arm64/boot/dts/qcom/sdm845.dtsi | 21 +++++++++------- >>> arch/arm64/boot/dts/qcom/sm6115.dtsi | 37 +++++++++++++++++----------- >>> arch/arm64/boot/dts/qcom/sm6350.dtsi | 31 ++++++++++++++--------- >>> arch/arm64/boot/dts/qcom/sm8150.dtsi | 21 +++++++++------- >>> arch/arm64/boot/dts/qcom/sm8450.dtsi | 22 ++++++++++------- >>> 7 files changed, 102 insertions(+), 63 deletions(-) >>> >>> diff --git a/arch/arm64/boot/dts/qcom/sdm630.dtsi b/arch/arm64/boot/dts/qcom/sdm630.dtsi >>> index 5827cda270a0..2aed49104d9d 100644 >>> --- a/arch/arm64/boot/dts/qcom/sdm630.dtsi >>> +++ b/arch/arm64/boot/dts/qcom/sdm630.dtsi >>> @@ -1330,9 +1330,8 @@ opp-200000000 { >>> sdhc_1: mmc@c0c4000 { >>> compatible = "qcom,sdm630-sdhci", "qcom,sdhci-msm-v5"; >>> reg = <0x0c0c4000 0x1000>, >>> - <0x0c0c5000 0x1000>, >>> - <0x0c0c8000 0x8000>; >>> - reg-names = "hc", "cqhci", "ice"; >>> + <0x0c0c5000 0x1000>; >>> + reg-names = "hc", "cqhci"; >> >> I believe this will break the ICE on these platforms without valid >> reason. The commit msg does not explain why you do it or why this is >> necessary. >> >> We already we received comment that we keep breaking Qualcomm platforms >> all the time and need to keep them in some shape. >> >> Also, patchset is non-applicable in current set (breaks users) and >> neither commit nor cover letter mentions it. >> > > FWIW, I tested this patchset on SDA845, and ICE continues to work fine. Really? I clearly see of_find_device_by_node -> "return NULL" and all old code gone, so ABI is broken. Are you sure you applied patch 1-6 and ICE was working? > > (Though if I understand the patchset correctly, the ICE clock is no longer > turned off when the UFS host controller is suspended. That isn't ideal as it > wastes power. I would like that to be fixed.) > > Anyway, when you say "break the ICE", do you really mean "make an incompatible > change to the device-tree bindings"? It breaks existing users of DTS and kernel. > > I'd think there would be no problem with that as long as everything is updated > at once, which this patchset does. Which is obviously not possible. DTS always goes separate branch, always. It cannot be combined with code into the same branch! So how do you even imagine this? > > I've heard before that some people consider the device-tree bindings to be a > stable UAPI. That doesn't make sense to me. It is stable ABI. Bindings and DTS are used by other firmwares, bootloaders and systems. The kernel *must* work with old and out of tree DTS. Even if this does not make sense to you, these are the realities, practice and current rules. > Actually, my original ICE patches > ran into this issue too, and the resolution was simply that the Qualcomm > platforms maintainer (Bjorn) decided to take the patches anyway. I never heard > any complaints afterwards. Maybe the same is fine here too? No, it is not fine. The patchset breaks ABI, breaks existing kernel with old DTS and breaks other projects using DTS and bindings. Best regards, Krzysztof