Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp8587724rwb; Tue, 13 Dec 2022 08:06:28 -0800 (PST) X-Google-Smtp-Source: AA0mqf6ffTgytabsHJN3yLdyus26WesTgDtR8GbpEIFCGst8T8WyllO2sh/yLVnRmyYP6Kc213Ko X-Received: by 2002:a05:6402:289c:b0:461:bf47:ba43 with SMTP id eg28-20020a056402289c00b00461bf47ba43mr22694728edb.28.1670947588450; Tue, 13 Dec 2022 08:06:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670947588; cv=none; d=google.com; s=arc-20160816; b=wvgylcJBcwu0im7OLrAQE554FrvMEbVW6OV7XSrAwdOBkiMsYqB2JI3XsffsuF8vBW Dsf+0S3hSwEA6wxg0ypfedW6XQaAO+AddhemfYH7MDUvQJoIz161BlcPgrmHmHx/tfJX omO/YiYLn0WBi31sEz96qnTuACdCPXLFsPrhMugm4HQCXQP+9RNI+NzkFsdUo2Io5FGP PweseyWJEsPkW0FLOwnO7fXigEmraQEW6FDG7xyxsVV/GTF3KvMeYzZrwTeSx3k4Y6sT rLAgHOngcY6Y2+zcq0ZpH2H/HgzuUumuOib62InXlBOmzxJ4wK2MVnqsuPmsUDAGHhV/ cD9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=PXK6uZcXfzeG+DbwnpKXeePgtYrWb0S4grr6umI7Kuw=; b=NuMNAKtQio9IXBG7F1Wq98CsVt2NGSnU186ctl/Wx4NsCQtQXftqBCSYq9d1AyJK4P FUCQI1kH0DbrdHSGjwt2Oa6VdS00OSzT3HdaIkaAqjEV7zs8e34fVOs5uKpD1qfoeFNw r1dTHwZURrbo26Z3KLdLnzwTnuHR5vw+U5FfmLMmoG4IS2s9l73qNp20MN7fpDm4v8iW vslJ9N2ZuBnKewzi+C5+0GwMv5SsViETtcGw4KjIPsuw9iwsZ1P1Ez++neGfIenX+MSn 2MKJ65CfIJa1TYwuxrhR5PgTG825lxA6TIwNFBHMm+UKLJUFBjLxd3A+K7q27e6hX1ma /Xfw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=maU9wZoz; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d9-20020a50fb09000000b004597671e0ddsi8440376edq.338.2022.12.13.08.06.10; Tue, 13 Dec 2022 08:06:28 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=maU9wZoz; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235540AbiLMPje (ORCPT + 72 others); Tue, 13 Dec 2022 10:39:34 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38396 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229562AbiLMPjb (ORCPT ); Tue, 13 Dec 2022 10:39:31 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EB2F02F8; Tue, 13 Dec 2022 07:39:29 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 764EB615BA; Tue, 13 Dec 2022 15:39:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A6210C433D2; Tue, 13 Dec 2022 15:39:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670945968; bh=BikuhlLcpULmvZ8vJt/sfoYfKYoTYubOFmvQ+RZ8I8k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=maU9wZozhg3uL6XAEm/N2Eywax2RDrQwVvOnAcemENR+QvPeD/jWbLc+Xb9l5mQH+ o/rCi5Q5h45hZI3daVO10gVXHzuLyR3DXW5K3pVrPVigGZGdZFrzes3XZc/vGsGouN oRhIo5cUc7qQB2LjwEy+1cchdGvRHChR8KpqfOKWre3T9FM+kMxp0JjaYO7Eh4zMNV B971xV7cAimFrxeBtJYXi9uZ/gF4DBhfkZ2b7J6yhWXHfBmbOkYEYa3XG+NuO46Anp ZtJ01XcmWNThrIj2p4gWXpT3jbcyEWT4ZQUWjbtOXjiVYKiG/3LRzTZO96TvcBlVaA 6AP8z3WJop4KQ== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from ) id 1p57Nq-0005M0-Pa; Tue, 13 Dec 2022 16:39:54 +0100 Date: Tue, 13 Dec 2022 16:39:54 +0100 From: Johan Hovold To: Shazad Hussain Cc: Brian Masney , andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org, konrad.dybcio@linaro.org, robh+dt@kernel.org, johan+linaro@kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, ahalaney@redhat.com, echanude@redhat.com Subject: Re: [PATCH 1/4] arm64: dts: qcom: sc8280xp: rename i2c5 to i2c21 Message-ID: References: <20221212182314.1902632-1-bmasney@redhat.com> <20221212182314.1902632-2-bmasney@redhat.com> <03252ccd-e200-a112-b4dd-ba9fbf25c480@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <03252ccd-e200-a112-b4dd-ba9fbf25c480@quicinc.com> X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS 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 Tue, Dec 13, 2022 at 09:04:39PM +0530, Shazad Hussain wrote: > > > On 12/13/2022 8:58 PM, Johan Hovold wrote: > > On Tue, Dec 13, 2022 at 10:12:57AM -0500, Brian Masney wrote: > >> On Tue, Dec 13, 2022 at 03:54:05PM +0100, Johan Hovold wrote: > >>> Note that the node is labelled qup2_i2c5 and not qup_i2c5. > >>> > >>> That is, the QUP nodes are labelled using two indices, and specifically > >>> > >>> qup2_i2c5 > >>> > >>> would be another name for > >>> > >>> qup_i2c21 > >>> > >>> if we'd been using such a flat naming scheme (there are 8 engines per > >>> QUP). > >>> > >>> So there's nothing wrong with how these nodes are currently named, but > >>> mixing the two scheme as you are suggesting would not be correct. > >> > >> Hi Johan, > >> > >> What would I use for the name in the aliases section? Right now I have: > >> > >> aliases { > >> i2c18 = &qup2_i2c18; > >> } > >> > >> So qup2_i2c18 becomes qup2_i2c2. Would I use the flat naming scheme for > >> the alias like so? > >> > >> aliases { > >> i2c18 = &qup2_i2c2; > >> } > > > > Or perhaps the i2c controllers should use a zero-based index instead of > > being named after the serial engines (e.g. as we do for the console > > uart). > > > > How are they named in the schematics? > > We should use from 0 to N. With N being 23 after the number of serial engines, or the number of available i2c buses on a particular board minus one? Johan