Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp532898pxj; Thu, 17 Jun 2021 08:10:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzgB5xKspDkYpS61Vfd8Brqs64hEgxClaFoSsNcZl9l9rTiilFJReMlOVoDhplVk3EuaP2N X-Received: by 2002:a92:b0c:: with SMTP id b12mr3700406ilf.123.1623942645025; Thu, 17 Jun 2021 08:10:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623942645; cv=none; d=google.com; s=arc-20160816; b=a6MDKNGtMwYAWdz+XO3Ya28eCzb65UUOu0KSkx2LEm4N01qs0QEtD5gq7uOFsMQRnh CUUUQr1AS0EDFfBm7YIlb1EIOU+TDTYu2+aF65BvCiCwe/PD9A3JaP/fhqQX5DmEYYCc ZWHAsxKsU1E7wqxvKMdxFDC8dW354xvdfLOAt/6vMDHRgoTUduTA1Zd5c7nJrFuK0J7x 5jfKvpDlob5/y+/J72dFsEXnvMe0tcboaH2pRJmiwXLtuPjONQFHBxTMzmZ6UTZN6Kls nUvd/BAXVzJvFvxSardIyCbRSkUMDbnWbYsgggg/H3xkj+6g1CmzfV3j71WZB1PoiEfi AkXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=uJTGcAdupVs9Ugv04FHACXamoJzkCvHB9LUInm949rQ=; b=i6pc8qnh7otAS26OYcntAF7n3WFw97dUAL9S3u+pKP73UzNJXirw8EdEQndvMIx1Ef CrMy0tnAKvpyDAy2xVLKSRdIGn85qyx8Pdy3yJv5re4r0BTSbB2OvizVQq3Nh4SWFxI+ TB9Gg0dFro9N1/V5HiZRYDKnEw5vYdtQkSaJOr98c2oRMs1krnGGdPVyKfEIYF64Load LIm/rAG3BOkxwdJDyiBQaVEcr3yyUw0wTbdQcAkK0UXFNwrtitptsNb7TCLdXqg44dKe tAoJ7w7I8ahmRKGemT5N/O9/uEbdVrsPIIC8vXV8E9L3un10nF/h1j6ipJPC0rYrxPyH bCfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@marek-ca.20150623.gappssmtp.com header.s=20150623 header.b=0kwTwa8f; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e1si5355663ilu.2.2021.06.17.08.10.27; Thu, 17 Jun 2021 08:10:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@marek-ca.20150623.gappssmtp.com header.s=20150623 header.b=0kwTwa8f; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233129AbhFQPLf (ORCPT + 99 others); Thu, 17 Jun 2021 11:11:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45346 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233059AbhFQPLb (ORCPT ); Thu, 17 Jun 2021 11:11:31 -0400 Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AE706C061760 for ; Thu, 17 Jun 2021 08:09:23 -0700 (PDT) Received: by mail-qv1-xf2e.google.com with SMTP id f16so969039qvs.7 for ; Thu, 17 Jun 2021 08:09:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marek-ca.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=uJTGcAdupVs9Ugv04FHACXamoJzkCvHB9LUInm949rQ=; b=0kwTwa8f3hL8cWbkSabeU4ie2c9poFkRbJwAggFGl/9viq04wZmf6V6XbbKd1TiAnN jCXYwWonNLnHSk4ogPtzJpv/SkyQOz9+jlMxA0jXywR3iIFgFUTH+dvFrnDJkQnSZJcB 6WnI5/68gIlAVUn/yb4Dih1Nsp9TIuYps08ChmTbRaAuXAknAaLXwVeSl6zQXPc3lXgj ksQTS8LFPtiSlkkEb6rHbt7q1V8obRSc6xpK6B55Ma0BMqvqakvbu9B7Gq/7fSKZvIun KMbI5DWSAyKE5FDiAeI7NttzZCF6KjWOgp7X3zeCgz7HsDUorQ3YkXnXjdho/4uGL/3x oc5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=uJTGcAdupVs9Ugv04FHACXamoJzkCvHB9LUInm949rQ=; b=eFwyh/cVNKUxueJhRlEQWGgjglsnDT0+mJvkv82NRq6+vroDVanUGwSilvV93j5QvY YpAs5ROu5mk3y/dmkPwRdh0LRnjKOM8KOHWxD93S5GgjbsbdoPK9GunfjvbsN9j2IFzx 7ZatqXixPAaGHAf0e0f36BYFzain+ViqiJIiIJq70vp61D1eeCWSs/jJSo+n24+XsV5x pQTaWHGBr2WQ+C6sM7OUIa6918xapY0unCoMjf1GuTMOYzfPtqCdoqoWHWIAmHFgyuWL 7X53Fur0jGUOrMJWmV/T8/cd7reMiUMy4JIifigvo6R2v+ZhXGvcL2BFmTPMXhe0fHre b7sA== X-Gm-Message-State: AOAM531MMH9gi2pNGErO9t4cElvqE5igDVy5y2sl0y5Rt/3Os+dULPdq v2OwrfnUuiDwCBj6x36HateOIQ== X-Received: by 2002:ad4:4772:: with SMTP id d18mr342093qvx.35.1623942562870; Thu, 17 Jun 2021 08:09:22 -0700 (PDT) Received: from [192.168.0.189] (modemcable068.184-131-66.mc.videotron.ca. [66.131.184.68]) by smtp.gmail.com with ESMTPSA id h17sm3297933qtk.23.2021.06.17.08.09.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 17 Jun 2021 08:09:21 -0700 (PDT) Subject: Re: [v1 1/3] dt-bindings: msm/dsi: Add yaml schema for 7nm DSI PHY To: rajeevny@codeaurora.org, Rob Herring , robh+dt@kernel.org Cc: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, sean@poorly.run, robdclark@gmail.com, abhinavk@codeaurora.org, kalyan_t@codeaurora.org, mkrishn@codeaurora.org References: <1622468035-8453-1-git-send-email-rajeevny@codeaurora.org> <1622468035-8453-2-git-send-email-rajeevny@codeaurora.org> <20210601205848.GA1025498@robh.at.kernel.org> <27dec6f881a3b8bd5e13ba32990f975b@codeaurora.org> From: Jonathan Marek Message-ID: Date: Thu, 17 Jun 2021 11:07:07 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <27dec6f881a3b8bd5e13ba32990f975b@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/16/21 1:50 AM, rajeevny@codeaurora.org wrote: > On 03-06-2021 01:32, rajeevny@codeaurora.org wrote: >> On 02-06-2021 02:28, Rob Herring wrote: >>> On Mon, May 31, 2021 at 07:03:53PM +0530, Rajeev Nandan wrote: >> >>>> + >>>> +properties: >>>> +  compatible: >>>> +    oneOf: >>>> +      - const: qcom,dsi-phy-7nm >>> >>> When would one use this? >> This is for SM8250. >> >>> >>>> +      - const: qcom,dsi-phy-7nm-7280 >>>> +      - const: qcom,dsi-phy-7nm-8150 >>> >>> These don't look like full SoC names (sm8150?) and it's >>> ,-. >> >> Thanks, Rob, for the review. >> >> I just took the `compatible` property currently used in the DSI PHY >> driver >> (drivers/gpu/drm/msm/dsi/phy/dsi_phy.c), and added a new entry for >> sc7280. >> A similar pattern of `compatible` names are used in other variants of the >> DSI PHY driver e.g. qcom,qcom,dsi-phy-10nm-8998, qcom,dsi-phy-14nm-660 >> etc. >> >> The existing compatible names "qcom,dsi-phy-7nm-8150" (SoC at the end) >> make >> some sense, if we look at the organization of the dsi phy driver code. >> I am new to this and don't know the reason behind the current code >> organization and this naming. >> >> Yes, I agree with you, we should use full SoC names. Adding >> the SoC name at the end does not feel very convincing, so I will >> change this >> to the suggested format e.g. "qcom,sm8250-dsi-phy-7nm", and will >> rename the >> occurrences in the driver and device tree accordingly. >> Do I need to make changes for 10nm, 14nm, 20nm, and 28nm DSI PHY too? >> Bindings doc for these PHYs recently got merged to msm-next [1] >> >> >> [1] >> https://gitlab.freedesktop.org/drm/msm/-/commit/8fc939e72ff80116c090aaf03952253a124d2a8e >> >> > > Hi Rob, > > I missed adding "robh+dt@kernel.org" earlier in this thread. > > Please check my response to your review comments. Regarding your > suggestion to use ,- format for compatible property, > should I also upload a new patch to make changes in 10nm, 14nm, 20nm, > and 28nm DSI PHY DT bindings? > > Thanks, > Rajeev > Hi, I missed this and ended up sending a similar patch a week later (as part of my cphy series, because I needed it to add a "phy-type" property). "qcom,dsi-phy-7nm" and "qcom,dsi-phy-7nm-8150" aren't new compatibles, they were previously documented in the .txt bindings, which are getting removed, but the new .yaml bindings didn't include them. Documenting them is just a fixup to that patch [1] which is already R-B'd by RobH (and has similar compatibles such as "qcom,dsi-phy-10nm" and "qcom,dsi-phy-10nm-8998 "). You can use a different/better naming scheme for sc7280, but changing the others has nothing to do with adding support for sc7280. [1] https://gitlab.freedesktop.org/drm/msm/-/commit/8fc939e72ff80116c090aaf03952253a124d2a8e