Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1209310pxb; Wed, 10 Feb 2021 02:56:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJzUy2UH1c+J/X08rTxHJC7IThJ05mRmwFTSIfInz9X1mKs40toMTyCY7rA9qjPptkHzkZCL X-Received: by 2002:a05:6402:2216:: with SMTP id cq22mr2569581edb.125.1612954596633; Wed, 10 Feb 2021 02:56:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612954596; cv=none; d=google.com; s=arc-20160816; b=hxzomz1kmTtlmXMxmA5VrSXoKUMTyWAQmDpheFDmZGe2Aq77GcQs/IkpK0IvHceAyk DjEABP4tzzYqhTxZafsdsjYws/IeXkCBv/UPpxNrKRc0fbuZ86nsEbEsbvt8J5OsRMSI vqg9R+IqXvPqI+DlCIr4ozE/MX9bLySbqUjWODZIv391gikc1gU5E6Jc0LiTiZOd6SnP CGuLvM31YeYJ7Zcq5Rr+24Vd9o3LHW7a3Fvyo+YxsP/rGHEtFx9W7dExXVm5gEPKEvJg 9QWRqqzZ5EBnNQAPWzzOGG6CO2LsBrv/Y7dDDZtH4hbg+yCvMXXCZYwvDtBfgAHM4fUn CDcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=wMnI7CMfVq8ZT8+poE1wdfCBH2bZ8hV4EqxR7V3tiXM=; b=EHcUT593RJAumfwcIKhw7zbMYfG9GumD5NZLM9M5CU/MyNIyoCR+TWG3MerSLRcv// e/kgf+Z/v2ZXdvhtMZ98ZnxM3fYj+blihE4zND11oOUK8ZvEBUWYXITx1YuwxLnz+dsK ZSNandIJbpXdQSs0G/30ZEJe0cw8zHIgvJNZvLwtrymb23rBmwFwZUClIuFgnZrKsMWF pXMxceX6C/WYqyQdvNqMhNUkhqF2MKd/79Vk7vaeTVB2b4QdxmnGvzpM7mYh/x4VyRGF 2cVQdwtlhXiygbGlWeA+xFxrb2B4Os3BDYsvtBMccvbBG6y1l1qiFO9VQReipF5yAGj1 peNA== ARC-Authentication-Results: i=1; mx.google.com; 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 u9si816064edd.431.2021.02.10.02.56.11; Wed, 10 Feb 2021 02:56:36 -0800 (PST) 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; 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 S229666AbhBJKxX convert rfc822-to-8bit (ORCPT + 99 others); Wed, 10 Feb 2021 05:53:23 -0500 Received: from gloria.sntech.de ([185.11.138.130]:43390 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231518AbhBJKuM (ORCPT ); Wed, 10 Feb 2021 05:50:12 -0500 Received: from [95.90.166.74] (helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l9n3f-0003Yx-RQ; Wed, 10 Feb 2021 11:49:19 +0100 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Arnd Bergmann Cc: Johan Jonker , Rob Herring , "open list:ARM/Rockchip SoC support" , DTML , Linux ARM , "linux-kernel@vger.kernel.org" , Robin Murphy , robh+dt@kernel.org Subject: Re: [PATCH 2/5] ARM: dts: rockchip: assign a fixed index to mmc devices on rv1108 boards Date: Wed, 10 Feb 2021 11:49:17 +0100 Message-ID: <46108228.fMDQidcC6G@diego> In-Reply-To: References: <20210118155242.7172-1-jbx6244@gmail.com> <6598201.ejJDZkT8p0@diego> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, 10. Februar 2021, 11:34:41 CET schrieb Arnd Bergmann: > On Wed, Feb 10, 2021 at 12:50 AM Heiko St?bner wrote: > > Am Dienstag, 9. Februar 2021, 23:25:40 CET schrieb Arnd Bergmann: > > > > Hmm, right now I don't see the disadvantage of missing mmc numbers. > > It's inconsistent with the normal use of these aliases across other > platforms. > > > As similarly we count i2c and serial numbers for a long time, even though > > not all of them appear on every board. > > Yes, that is a similar mistake. > > > Especially as the main goal is to simply have stable numbers and > > not having the mmc devices swap numbers on every boot. > > > > So right now we're not using them from a userspace POV but > > instead agreed on following the address ordering of the soc. > > so when ordering mmc controllers by their io-address, mmc0 > > is the first one, then mmc1, etc. > > > > So just for my understanding, what is different for mmc? > > I guess to guarantee ongoing numbering similar to sd{a,b,c,...} > > Or should all aliases be duplicted in each board dts and not > > live in any soc dtsi? > > Each board should have its own aliases node that describes > exactly which of the devices are wired up on that board, and > in which order. If there are connectors on the board that > are labeled in some form, then the aliases are meant to > match what is written on the board or in its documentation. Then we're at least in the clear for i2c, serial and the rest ... as these are numbered in the soc documentation, and all boards I've seen so far use these number also to identify these in schematics. So an i2c2 is always i2c2 even if i2c1 is not populated. And of course doing i2c0 = &i2c2 would definitly confuse people to no end. So I guess we'll just move the mmc stuff over to board files.