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 E8CD5C43334 for ; Wed, 29 Jun 2022 18:58:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231210AbiF2S6O (ORCPT ); Wed, 29 Jun 2022 14:58:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43212 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229838AbiF2S6L (ORCPT ); Wed, 29 Jun 2022 14:58:11 -0400 Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 116321A050 for ; Wed, 29 Jun 2022 11:58:06 -0700 (PDT) Received: by mail-lj1-x22a.google.com with SMTP id c15so7153926ljr.0 for ; Wed, 29 Jun 2022 11:58:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:user-agent:in-reply-to:references :message-id:mime-version:content-transfer-encoding; bh=QYZAgrfhk49lzLUuFjw6B1O7Zz6sl6FqL+L4Ejbb/r4=; b=qSia/dWyaWJ9BNfd7r3B8IDOa994IYlAmU2aa/+oHVn4fpjphPOg7L6/tfkI33z7A8 us7a5wZ1HFmxvyYimOJZU3qWHVq6OcOh1M25XTuc+C6KasU77ONzrIIFv5UPyZ55YbHL Z4bdq5el5TRvSCUUpcdXvlYLmsW4OEN+HB3tZYEJUgqeaHBNclIOScCLN7QW4TiEyM+a de9SGChXZ6LdTUXNFe3jzLLGwyQpFp3EgUcnJy28POPwlaxh0R3yQvKYfGRwif2g95JZ GhRqPMWDzN5U1bRyHexW1YkQ/+GzhdO04ePNp1WZmranQ7B645Zd1Qxu8UGnhcfTebHe TFVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:user-agent:in-reply-to :references:message-id:mime-version:content-transfer-encoding; bh=QYZAgrfhk49lzLUuFjw6B1O7Zz6sl6FqL+L4Ejbb/r4=; b=Qmuoia5aFL6pnODW6081tuJ6oArf508Uw/Hvk/uBp7NBsyJxJsBFFBiH0Oe70P4XqG JiVacAc5h2PGWYfN7p4+/vqGdcuUxOI6ueKafCtRPk3RVgV96WuXklqREpYwe7CpfLGw dtY+C/ewE2iJIwXSdcW3Dh6fIwQ2lyuHD+tGXOsbypTb8LoyMzJMEaNySFwm9uxFKjft 2yJ07Dm5lpKGbjUWozfvuqSvVZN7Q3pdvG9RCRXafxCATmwdC1AfUfm7IvpttE65kcal FeioZqPEvfwThTKesBvi8GEhaN4o2ErXTvm0X6eBAEt769fgoWUUpuswhlpYIB0xKxZ1 rzHQ== X-Gm-Message-State: AJIora/vi3t1j6zXSoOIN4GeyoiGiYtqeGi+aLxwiXC8NMDfEHaBXkhv IvQEeLj59TrC6zenxeXLJbikZjQsGDCsTA== X-Google-Smtp-Source: AGRyM1vK3aRgMtM4vp3JC8oLZ1h6/8DljR5JiFPtpWzVEDfclPLBY/0pg6p1L99EUupCdECV+pl1BQ== X-Received: by 2002:a2e:8552:0:b0:25a:99bd:5f9e with SMTP id u18-20020a2e8552000000b0025a99bd5f9emr2821338ljj.519.1656529084357; Wed, 29 Jun 2022 11:58:04 -0700 (PDT) Received: from [127.0.0.1] ([94.25.229.210]) by smtp.gmail.com with ESMTPSA id h15-20020a2eb0ef000000b00255500154fasm2248617ljl.52.2022.06.29.11.58.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Jun 2022 11:58:03 -0700 (PDT) Date: Wed, 29 Jun 2022 21:57:58 +0300 From: Dmitry Baryshkov To: Krzysztof Kozlowski , Rob Herring CC: Andy Gross , Bjorn Andersson , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, Krishna Manikandan , AngeloGioacchino Del Regno Subject: =?US-ASCII?Q?Re=3A_=5BPATCH_08/11=5D_dt-bindings=3A_displa?= =?US-ASCII?Q?y/msm=3A_add_mdp-opp-table_to_dpu-sdm845?= User-Agent: K-9 Mail for Android In-Reply-To: <6e1b37e6-83e8-a920-61d9-044b08e93605@linaro.org> References: <20220625232513.522599-1-dmitry.baryshkov@linaro.org> <20220625232513.522599-9-dmitry.baryshkov@linaro.org> <20220627180506.GA2679395-robh@kernel.org> <772E0163-AC47-47E1-A0C6-CA04CA874282@linaro.org> <6e1b37e6-83e8-a920-61d9-044b08e93605@linaro.org> Message-ID: <5407A5CD-D8AF-41B3-9F16-67A30940D844@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 29 June 2022 12:23:48 GMT+03:00, Krzysztof Kozlowski wrote: >On 28/06/2022 22:23, Dmitry Baryshkov wrote: > >>>> + $ref: /schemas/opp/opp-v2=2Eyaml# >>>> + >>>> ports: >>>> $ref: /schemas/graph=2Eyaml#/properties/ports >>>> description: | >>>> @@ -116,11 +120,12 @@ examples: >>>> <0x0aeb0000 0x2008>; >>>> reg-names =3D "mdp", "vbif"; >>>> =20 >>>> - clocks =3D <&dispcc DISP_CC_MDSS_AHB_CLK>, >>>> + clocks =3D <&gcc GCC_DISP_AXI_CLK>, >>>> + <&dispcc DISP_CC_MDSS_AHB_CLK>, >>> >>> What does the OPP table have to do with clocks? Adding a clock anywher= e=20 >>> but the end is an ABI break=2E >>=20 >> I should split this to a separate patch=2E And, I must admit, this cloc= k change has already landed=2E We did not think that it is an ABI break sin= ce we have clock-names here=2E > >xxx-names are only a helper and order of items is always strict, thus >any change in the order is always ABI break=2E Ack, we will keep this in mind=2E However in this case we have already mad= e this change=2E So the question in his do we cope with it=2E --=20 With best wishes Dmitry