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 CE96EC38142 for ; Mon, 23 Jan 2023 15:49:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232910AbjAWPt2 (ORCPT ); Mon, 23 Jan 2023 10:49:28 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232606AbjAWPt0 (ORCPT ); Mon, 23 Jan 2023 10:49:26 -0500 Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C23EC15567 for ; Mon, 23 Jan 2023 07:49:24 -0800 (PST) Received: by mail-wr1-x434.google.com with SMTP id e3so11201967wru.13 for ; Mon, 23 Jan 2023 07:49: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=oRrlO1y0MQCgeVJ1C8FCZsk1QyUHS9Bge/H7XBbj9NE=; b=swDVpyA/cOqgd3BzwtL9dhxt8H4pjMIL0rkk6nBLIs34KHHA1zYpIAqLXYNFxrRLhn VWjyFKwr33BcWOCn2AcobEf1bcI1u5v+3/KQqdD9uTIn6jyX/uK3VdIYAAxov0Tv7HOA fLi9bCDGGW8azvBu5b075KGms0op8mme1Jhm0BBUY4ndfcThuVLAMoZOQ5+Zw4IK3w+Z vCA3PD4QELkUITjrC/cnvYHRs4/9i03RpTGOmvscyHjuWSNlBEcbmAgcPWSwlwrrwBBg zOSCOWyKzS2u4qgUXHE0xwXQQ/PbW+ev8hLSlz5HCUAjRF6kLSUJWfcuFw8zGu0gO+Eg rZQw== 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=oRrlO1y0MQCgeVJ1C8FCZsk1QyUHS9Bge/H7XBbj9NE=; b=z2qukdiro9wg+7SmN9qNiZBvWVrPa1tcK9GVgqK1Sj6cyC0hmUvwYnAWda0x6Flht0 XqLLuMVZr2POxyg0sO1JKNVxJdGVi/FA21Csu+LcQ9WbtvBSt82amYxOETqbYe/p3Jtn qU4VGolXlqmff3Qt4BLE93xyeYzOctqMSP0dz1REvvgelgnD8JdNhk+d3Wm56zjJNswE 6viyMn1tYnqUoLc/jHkvLc1MShCenku2agbcJfAlaLtMJP2AYZ/UyKBest3GehfJTLrw 8P4xVBQR4B5LayN4Kr33FcQm8PKyiiqUSX+Onoo63JiaxkC4QilMeMCo4Vw9Cfj5564N KyLQ== X-Gm-Message-State: AFqh2kodc8oIj0I0Y9kocdFkZV84+fu/86notSI595dzymvaSt79RfH2 M9NnQr8p8+qq8J6TeuyFd3pLgv8cg9+fX56Y X-Google-Smtp-Source: AMrXdXvj7CKw9kx7uw6aIqK5wdSyxxpICiQJ8Y8+j8LTwjVqZp2eJmwSRdZfJ2o5Nu3o2AvA1xlLSg== X-Received: by 2002:adf:dd84:0:b0:2be:4fbe:42d5 with SMTP id x4-20020adfdd84000000b002be4fbe42d5mr13917911wrl.5.1674488963364; Mon, 23 Jan 2023 07:49:23 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id w5-20020adfcd05000000b002bdc914a139sm35089639wrm.108.2023.01.23.07.49.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 Jan 2023 07:49:23 -0800 (PST) Message-ID: Date: Mon, 23 Jan 2023 16:49:21 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.0 Subject: Re: [PATCH 1/3] dt-bindings: arm-smmu: Fix binding for SDX55 and SDX65 Content-Language: en-US To: Manivannan Sadhasivam , andersson@kernel.org, will@kernel.org, joro@8bytes.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org Cc: konrad.dybcio@linaro.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, iommu@lists.linux.dev, dmitry.baryshkov@linaro.org References: <20230123131931.263024-1-manivannan.sadhasivam@linaro.org> <20230123131931.263024-2-manivannan.sadhasivam@linaro.org> From: Krzysztof Kozlowski In-Reply-To: <20230123131931.263024-2-manivannan.sadhasivam@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 23/01/2023 14:19, Manivannan Sadhasivam wrote: > Both SDX55 and SDX66 SoCs are using the Qualcomm version of the SMMU-500 > IP. But the binding lists them under the non-qcom implementation which is > not correct. > > So fix the binding by moving these two SoCs under "qcom,smmu-500" > implementation. > Acked-by: Krzysztof Kozlowski Best regards, Krzysztof