Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp8573657rwb; Tue, 13 Dec 2022 07:58:44 -0800 (PST) X-Google-Smtp-Source: AA0mqf6rxrfHFCUrL097++eOvq8uA08FV5NN75yseNKYfmnR6JHvRbxE26Y+ZepWnorygjdZR83Y X-Received: by 2002:a05:6402:1693:b0:46c:91fa:5a7d with SMTP id a19-20020a056402169300b0046c91fa5a7dmr18803156edv.12.1670947123852; Tue, 13 Dec 2022 07:58:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670947123; cv=none; d=google.com; s=arc-20160816; b=PtROLCd0RTZ8AsV8UdsWESgKxoZEz4UAKw2eYDBU4YcJAxV00hbf6rXdmIa3W+xsGy N5uuASa8lTwrpqAxj0E859ktiNNJM6XMOWcIz75bIBT4PVqLwndszf3cRl/3ivDFxkzr A9UhDxmiSVwUTIhb53qKgWmHFrjePlg7kVQsin+T8OMOjCh9maTqxS4OoLtJDZvLCNdi IgROa8p1bS1kWhezHhdUp0Q1sdUSI6PF9kYxkwg4UMd2y1aYAWU9vInIoYaHa/u2yvVi iGwwQH3p6bvzGFR/JBRUIPoihdzjyuHSqIy7K0E92Cunk8egNF60e9CSLCVuLT6UhDPH Yw5Q== 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=il9d1mACAjDE0rxRgpeOVU440ySY0I4nA6rs2uoOm2c=; b=twHc3NJDWDbvt2/Prr4j5Zdu8mYiu4uE8QEXeYsZSdGkOo3b5VS2Y99cK9uW0mEB0y 2cGyZoCbrS+UeOA1JkMEHYNsQOFH4h4FwDlTT91iXSeMQpcAOjkyCTiddwSBEC9JNLYS BGgXDdo41CFFodttETkZiB3MLXcdAQEf3xFUUmcId4Itq+7VvhzdgDlYl6Sxd5a+vewu bkHTMziau+NNDH95GXOs1ORfxb4IzV61FslaDuS0fG+aYaxL6pCMTRw2a/Bb9ODh2b+Q HnKmx/JjJbW7+wzmzClmtk9olWFGkK//YTsQThd/dKoVWrT8KcV8mzfrTR/xTGa1ZYXz Loaw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=YUgRo65B; 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 q18-20020a056402519200b00469d667117csi11802607edd.167.2022.12.13.07.58.26; Tue, 13 Dec 2022 07:58:43 -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=YUgRo65B; 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 S235917AbiLMPRO (ORCPT + 72 others); Tue, 13 Dec 2022 10:17:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52928 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235161AbiLMPRL (ORCPT ); Tue, 13 Dec 2022 10:17:11 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B9BFA2098F; Tue, 13 Dec 2022 07:17:10 -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 ams.source.kernel.org (Postfix) with ESMTPS id 60247B811D8; Tue, 13 Dec 2022 15:17:09 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 06486C433D2; Tue, 13 Dec 2022 15:17:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670944628; bh=5QESWjudrIWVHyOcAlkl6YNsgZ0EkNBCvncmf6xjMOM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YUgRo65BwCx+hSWdf1niQ24ejHfuX4ek/krmnbk5Y1v1j7WdpaDyYAIBnIJj631Uz tzFdIJaiqguVn0mMztziVjKpKZ9SzAJCUT7DtLRyV5f5pK0Ti7TBD2/fnJfbSgtDHD msSLKTxGrOOgqXA++cj7KQRxIDpiM6wgfQmPSuLr7JRVis7xxDKtyGykNnhzGz0UHZ +FGOdLP5p6Q9XiE3SOpNvkWWrFC59lUTz0TBeCTf1OEOXT73s3L9XONWvnoWZgJqn7 03StvfYEVoWTs9WX463dfh0WKMGkvtrL5cRTUkqaIyOYHx55fktwPVZUp7c+zC/KBl P/nK0WdI9kkXw== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from ) id 1p572D-00053B-7H; Tue, 13 Dec 2022 16:17:33 +0100 Date: Tue, 13 Dec 2022 16:17:33 +0100 From: Johan Hovold To: Brian Masney Cc: 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, quic_shazhuss@quicinc.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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 03:54:05PM +0100, Johan Hovold wrote: > On Mon, Dec 12, 2022 at 01:23:11PM -0500, Brian Masney wrote: > > According to the downstream 5.4 kernel sources for the sa8540p, > > i2c@894000 is labeled i2c bus 21, not 5. The interrupts and clocks > > also match. Let's go ahead and correct the name that's used in the > > three files where this is listed. > > > > Signed-off-by: Brian Masney > > Fixes: 152d1faf1e2f3 ("arm64: dts: qcom: add SC8280XP platform") > > Fixes: ccd3517faf183 ("arm64: dts: qcom: sc8280xp: Add reference device") > > Fixes: 32c231385ed43 ("arm64: dts: qcom: sc8280xp: add Lenovo Thinkpad X13s devicetree") > > > diff --git a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi > > index 109c9d2b684d..875cc91324ce 100644 > > --- a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi > > +++ b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi > > @@ -827,7 +827,7 @@ qup2_uart17: serial@884000 { > > status = "disabled"; > > }; > > > > - qup2_i2c5: i2c@894000 { > > + qup2_i2c21: i2c@894000 { > > 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. It appears sc8280xp is the only qcom platform using a qup prefix (even if some older platform use a blsp equivalent), and we're not even using it consistently as we, for example, have both qup2_uart17, and qup2_i2c5 (where the former should have been qup2_uart1). So either we fix up the current labels or just drop the qup prefixes and use a flat naming scheme (e.g. uart17 and i2c21). Either way, there's no need for any Fixes tags as this isn't a bug. Johan