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 1BF16C4332F for ; Thu, 29 Sep 2022 14:38:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235738AbiI2Oii (ORCPT ); Thu, 29 Sep 2022 10:38:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60390 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235725AbiI2Oig (ORCPT ); Thu, 29 Sep 2022 10:38:36 -0400 Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3E1C11C00E0 for ; Thu, 29 Sep 2022 07:38:34 -0700 (PDT) Received: by mail-lj1-x230.google.com with SMTP id c7so1748203ljm.12 for ; Thu, 29 Sep 2022 07:38:34 -0700 (PDT) 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; bh=j0oWhXN2ZUd4COh7520YadSBs3lWzKCaGNiRYIIVCPU=; b=mcyHw/JXKkRWeKdTRipuWpdhKIdeRs7z/+yLr6sInNo7TR0aH42e14aN1KVAcXwe07 wT12VHvxJ0Nu68qak+4LfFZfC7jnigLtkosYoecDks+Os5/GwK7NTtPYA8G6C+3Nx5Hg xLkbm7oKmZC/wvq1Qg0BS00R91Z/ni6dBtUbVEQw3mHcyG/+U0cfTpGxBmwGUsWSLVEN CgxTyV5zipdVqylGNH/vlOeZbqaWqu7oScxfaCnVpb2QYsTWu12rzLC5h1jEelDihZ// dgos0d5J+C2AzkcUHk7etK7vgJvNEf2F2Q9VxNsQFoj7O/dSKw1YLLznQB/rDPIn2oFQ bWgw== 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; bh=j0oWhXN2ZUd4COh7520YadSBs3lWzKCaGNiRYIIVCPU=; b=2gWD+DUcXsYB7gNmMe6UrecufWeIfOrQJjZTZYkG267RiaDI0gqj1txwdf72vEgvWZ /n+PQ4rS29zr1CE/4RVzgO3/MN6zuvzecKeHXp/tLmUcm4Z5s8eea/IOBFXqjF4Hhi6Z UhVVUQ4ACiX+4RYodzHvo0vOy9Bv4661eK+00VSKM9J1NcSrfAwbra4feBkdCSxnz4Kv Z+jBI4EROfoyeFKIc390v4iF3AT38BEljefaDspS9VZMeTGWJtBJvqjpLzyeQ9yAx9wi KOE1VvkQ/oDn/o10kY6iZenWhyqaf/6wfVglVbTuTPjp8CbhpVm3J3uUggT91hW6MmY7 ygvA== X-Gm-Message-State: ACrzQf0O4YJDQF6Rna9srLRs0YXcS7j2e0EgG27RI2SX7hgQfIe+SLHd LlgtLWvMvQ4tnkDYOGily2QrbEfUCm12Ow== X-Google-Smtp-Source: AMsMyM6DfRuuk5kpoptytoVkIDXi2xRmhOg3yGtMP6fD6LB0TNCoWSpxXSG34U4iX5ZBnhCmC8HEPg== X-Received: by 2002:a2e:b744:0:b0:26c:40bf:eaba with SMTP id k4-20020a2eb744000000b0026c40bfeabamr1430188ljo.367.1664462312649; Thu, 29 Sep 2022 07:38:32 -0700 (PDT) Received: from [192.168.0.21] (78-11-189-27.static.ip.netia.com.pl. [78.11.189.27]) by smtp.gmail.com with ESMTPSA id c6-20020a056512074600b004948b667d95sm800772lfs.265.2022.09.29.07.38.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 29 Sep 2022 07:38:32 -0700 (PDT) Message-ID: Date: Thu, 29 Sep 2022 16:38:31 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.3.0 Subject: Re: [PATCHv4 1/3] dt-bindings: mmc: synopsys-dw-mshc: document "altr,sysmgr-syscon" Content-Language: en-US To: Dinh Nguyen , Ulf Hansson Cc: jh80.chung@samsung.com, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org References: <20220928165420.1212284-1-dinguyen@kernel.org> <20cbd2a2-752e-8537-4cbd-6665ef9afd69@kernel.org> From: Krzysztof Kozlowski In-Reply-To: <20cbd2a2-752e-8537-4cbd-6665ef9afd69@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 29/09/2022 16:20, Dinh Nguyen wrote: >> >> So this change will not be backwards compatible with existing DTBs. I >> noticed that patch2 updates the DTS files for the arm64 platforms, but >> there seems to be some arm32 platforms too. Isn't this going to be a >> problem? >> > > The arm32 platforms makes the clk-phase adjustment through the clock > driver. There was a discussion when I originally submitted the support > for the arm32 platforms, and we landed on going through the clock driver > instead of using the MMC driver. The updates to the arm32 platforms can > be done after this patch series. How the update "can be done after"? Didn't you break all boards in- and out-of-tree? Best regards, Krzysztof