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 7FAB6C433FE for ; Tue, 18 Oct 2022 15:32:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230335AbiJRPcW (ORCPT ); Tue, 18 Oct 2022 11:32:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48756 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230369AbiJRPcR (ORCPT ); Tue, 18 Oct 2022 11:32:17 -0400 Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C87C5D4A12 for ; Tue, 18 Oct 2022 08:32:10 -0700 (PDT) Received: by mail-qk1-x734.google.com with SMTP id t25so8866599qkm.2 for ; Tue, 18 Oct 2022 08:32:10 -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:message-id:reply-to; bh=G1/uDkzke1I9MIXgJReSc/5yrjYBWTdhHs4pK5HuUcU=; b=eU7bFamSLI28JsgdEar8LiWEMX6cc97/5zuKhkJeJI96D4MPCqmHgaUXqVhvD47bW1 A+wxdY1mbuEqCwwaHmNlZz5jqMtpS6XfsJg4eyRrmKtvtutpHVZfeeeU82AKjIcRHwbR zBspuDGnsCBnr06GRU9iP4HbzQk7me66qHm4DBgl1ZjhJjdT0+8FZB/doPw7kNA1O4fF R13sZi9dqR3SHx8H9/9woXnOdBZHbS4bro7KjScFRupf4n35o2J1ij8CPtYJ5sVYAjRw GWqwqj5FxwAQXMka1zN5L0WlOFNgCTFxjwQK1Hql7oFnh1JI1sg6F/9Sag0qsJsaJwhO TGMQ== 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=G1/uDkzke1I9MIXgJReSc/5yrjYBWTdhHs4pK5HuUcU=; b=kCcZt+FJIZeNBhG4RIz/hpOLMeO/mfMjwh8y6uLfEswlaKzRQ3eHVa6y25E5jdj1Rs b18zvxulUhwLAAoQh9TJsqGzGx7PtRFThAd8fDrslOg+zo0duMCoEOq3NNgzt89aAK3V c/skZcwPu1nbD/S0JesMdVmewur3DDfIVpWj7mMRN1axcj9NCbKf6KdA+u7yuG2ajAoI dEMZV4oj0dRshmGGIVxDxh8xeg2DTEr3ImR2Kqu6e/B3RaWHdYfNC7JL7pcSmAqdR+dK A1nkSgjRKgbw1WyDBnxFR6tkNAvJQYx64by2FHkN/FdxXix/i3Kb/ZEPZOM1VI1/Ka0e EIyw== X-Gm-Message-State: ACrzQf3ntQE+gp9/5OQJzswkkFhO5kGFFaE00jp2dz+TKKK73fZzRPX3 4RZuKUrS4Cz0RIFTYsV9y1GQbw== X-Google-Smtp-Source: AMsMyM7eVweGu17+jtxN0kMIKkC2qER56wGixOvLXX1kSLjhAlxUlN+fkkmcKGJrQWP5eMoSC3HGQQ== X-Received: by 2002:a05:620a:46a7:b0:6ee:dea7:cc1c with SMTP id bq39-20020a05620a46a700b006eedea7cc1cmr2303292qkb.506.1666107129262; Tue, 18 Oct 2022 08:32:09 -0700 (PDT) Received: from [192.168.10.124] (pool-72-83-177-149.washdc.east.verizon.net. [72.83.177.149]) by smtp.gmail.com with ESMTPSA id c25-20020ac81119000000b003996aa171b9sm2043401qtj.97.2022.10.18.08.32.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Oct 2022 08:32:08 -0700 (PDT) Message-ID: Date: Tue, 18 Oct 2022 11:32:07 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.0 Subject: Re: [PATCH 09/15] dt-bindings: phy: qcom,qmp-pcie: mark current bindings as legacy Content-Language: en-US To: Dmitry Baryshkov , Johan Hovold Cc: Johan Hovold , Vinod Koul , Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20221017145328.22090-1-johan+linaro@kernel.org> <20221017145328.22090-10-johan+linaro@kernel.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: linux-kernel@vger.kernel.org On 18/10/2022 07:37, Dmitry Baryshkov wrote: > >>> And yes, I think we should also upgrade >>> older DTs, keeping drivers backwards compatible (for some time?). >> >> Possibly, but I'm not sure it's worth the dts churn. As I mentioned >> elsewhere, supporting both the old and new binding in the driver is >> mostly trivial, while encoding the deprecated bindings in DT schema >> sounds like it would be painful. > > This is probably the time where Krzysztof can advise us. I'm still not > sure when it is expected to encode both old and new bindings in the > schema and when we can update both the schema and the DT. I do not follow what exactly the proposal is. Are you asking whether to: 1. keep existing DTS compatible with old driver? or 2. update existing DTS so it is working only with new driver (and not compatible with old driver thus having ABI break)? If so, it is less question to bindings but more to the usage of DTS in other projects (like bootloaders, firmware, BSD) and generic recommendation is: do not break other users, if possible. It is however up to the platform maintainer (Bjorn) to decide on this, not on me. Best regards, Krzysztof