Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp4950482iog; Wed, 22 Jun 2022 08:54:45 -0700 (PDT) X-Google-Smtp-Source: AGRyM1trzpgqgWMgaTA3rpG1m/PrKTEI7hmfH/ebvKewTrHb/nrPodlVBy0dWUgDW+32qusczRCH X-Received: by 2002:a17:907:9704:b0:711:f441:dbe6 with SMTP id jg4-20020a170907970400b00711f441dbe6mr3701185ejc.26.1655913285083; Wed, 22 Jun 2022 08:54:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655913285; cv=none; d=google.com; s=arc-20160816; b=YCXHedeHkv4gZ12Y99+lx2HovTB7Lonl9C6bZ496KFk2fmEYIq4Bjx9EXuanDqgpv9 bXGrToOVSkPuzmk3S96opuzrNuXqWq845G5El83m2HYxcaIRguFlg3BViEnFvDv2m91N sPb510hc1jCz2n4ZAO/9QeCZNgnvBzj6SAO4a7X9WgIQ8j9DFfmY2zb8Q//9sEHu3N0U hnW+NGo5plS/BaIuUPezJmpTL4pJzXEoc8b6KeWScJUrL4uuhi0SzflTOuszhkoBw2E6 EDqfvM3NY4sxmohwks8uRpIUQ1FiatSDf0G0I3bZvnSjBRHPSwMTNR8VeBQdvlZT7txc wGdw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=HLo1yVTul3ouQY/4/AQkbWQAh61YeEAhzmEB66FuErw=; b=jUIW4LQCEJoxpEfWsyxih6kyoVY1NeE+8j1fP7mfTTwzDnrP0v32dYKB7Q5bCaZJaP NxjHbMehTj8OctofrwkEIMh4mlfaHhiZn6FQQDL20m7kzCg5dTVY3der8G3z8o63RqUK grRvob1vaIwQ6uFwAFCMMTnC2W5kopXERCfxlMBNlSoFJHU0uNiFb585SMQkOg86GRLW nMHBKBIDwO0wZMIfxaHqA6tVOLi//BUUOCTzH/4pl9ZldHB6fFHBMmOaa8zzw0g4WXQL iFKTqqDMfirlJOYfC0O1oVRE6AA+nTdCZjnyGnljISSveE8k7iT3Cjp8OiGjPWvKpYx9 ECOQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id qc25-20020a170906d8b900b0071223d9f214si2168068ejb.177.2022.06.22.08.54.18; Wed, 22 Jun 2022 08:54:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1359170AbiFVPLA (ORCPT + 99 others); Wed, 22 Jun 2022 11:11:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44928 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1359111AbiFVPKy (ORCPT ); Wed, 22 Jun 2022 11:10:54 -0400 Received: from relay01.th.seeweb.it (relay01.th.seeweb.it [IPv6:2001:4b7a:2000:18::162]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5CC663DDFA; Wed, 22 Jun 2022 08:10:53 -0700 (PDT) Received: from [192.168.1.101] (abxi223.neoplus.adsl.tpnet.pl [83.9.2.223]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by m-r1.th.seeweb.it (Postfix) with ESMTPSA id 4C27420569; Wed, 22 Jun 2022 17:10:51 +0200 (CEST) Message-ID: <51965fa3-d146-70f1-2ad8-db6197989348@somainline.org> Date: Wed, 22 Jun 2022 17:10:50 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH v2 4/6] arm64: dts: qcom: sc8280xp: Add reference device Content-Language: en-US To: Krzysztof Kozlowski , Johan Hovold Cc: Bjorn Andersson , Andy Gross , Krzysztof Kozlowski , Rob Herring , Manivannan Sadhasivam , Jassi Brar , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220622041224.627803-1-bjorn.andersson@linaro.org> <20220622041224.627803-5-bjorn.andersson@linaro.org> <099cc82f-d52f-315f-189d-bcc40c1afd49@somainline.org> <9d0c1897-195f-0548-ea5d-ffc35768f518@somainline.org> From: Konrad Dybcio In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 22.06.2022 16:48, Krzysztof Kozlowski wrote: > On 22/06/2022 16:36, Konrad Dybcio wrote: >> >> >> On 22.06.2022 15:43, Johan Hovold wrote: >>> On Wed, Jun 22, 2022 at 02:33:02PM +0200, Konrad Dybcio wrote: >>>> On 22.06.2022 06:12, Bjorn Andersson wrote: >>> >>>>> +&qup2_i2c5 { >>>>> + clock-frequency = <400000>; >>>>> + >>>>> + pinctrl-names = "default"; >>>>> + pinctrl-0 = <&qup2_i2c5_default>, <&kybd_default>, <&tpad_default>; >>>>> + >>>>> + status = "okay"; >>>>> + >>>> I think all device DTs generally have 'status = "okay"' at the beginning. Should we change that? >>>> >>> >>> No, quite the opposite, status go at the end. >> Then all other device DTs should be updated, as in dts/qcom/ >> everybody keeps it first in non-SoC/PMIC files. > > The word "should" is a bit too much here, but I agree, we can update all > of them to match one, chosen approach. > > However the location for "status" property is more important for the > definition of nodes in DTSI, because it's the least important piece > there and also kind of expected - here go properties + I disable it. For > me this is more important. > > For node redefinition in DTS, I see benefits in two approaches: > 1. Let me first enable the node and then configure it. > 2. Let me configure the node and enable it. I looked around non-qcom device trees and it looks like the common consensus is 2. Although I personally visually prefer 1. and it's been used in all qcom arm64 DTs to date, I don't think there are any blockers for us to switch to 1. going forward to keep it consistent. That's if we want to clean up the existing ones, as changing the rules and not applying that to the older files will make for a huge mess as time goes on and will unnecessarily prolong the review process (as existing DTs are commonly a source of reference and people make certain choices based on those). I don't think the DTS specification or the Linux docs explicitly which one to choose though. Konrad > > Best regards, > Krzysztof