From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 084F1C433ED for ; Mon, 19 Apr 2021 02:52:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DE9ED610CB for ; Mon, 19 Apr 2021 02:52:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237338AbhDSCx0 (ORCPT ); Sun, 18 Apr 2021 22:53:26 -0400 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]:46837 "EHLO wout5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233117AbhDSCxT (ORCPT ); Sun, 18 Apr 2021 22:53:19 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id DAD8122DC; Sun, 18 Apr 2021 22:52:49 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 18 Apr 2021 22:52:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sholland.org; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=fm2; bh=ZSwc/xCZvaeAVu3WuRRMOZasHK iHtAPWRkPgguSoPCk=; b=HgeitUikCRe/M+RZedAxU5CwFWoNBH5yty/6dAVhhg 7WdZp/VBgtfMH455GCN8oNget7zvyXD5DYNYs2q1YmroOK1C02QaKXKziKaKgwkk y/o2pVNuK0aUAvWqHFOxkycQDVaWc98VrhdjtCycHke2Y2Qmjh6V/fjZLug40aSF gZcOCHiy4tzBdRhodb8p8fLSRUkG5nFIchslI9xVFr8+W/t6XFr++7QH8q1fdNDJ GKvBgE6WVVaneylx0K/OQLXYEgk2p9djFNFTe58CPLTDtrHbYED5yc4FHdoeGaQx R9aNfrGhFPrDMgHNaAPhRuHy78GnhAwlhD9V+cJT4fTw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ZSwc/xCZvaeAVu3Wu RRMOZasHKiHtAPWRkPgguSoPCk=; b=iJvpTIkXH7xtoHZpjac3yTq1SMoYVQFKy IUtxwGcWiBf21JqLWgQ7UKvoLlTodLFd6umAazZGAlFlSIISLv54sUpdl0ag+fr5 6Di+aXxoXNjNW2W6qI5C1wtvPNBr3BTJOvYj6G9dDVFd4uRfUQguvMMLvJ8R9Ph1 SXM6kVqkls0sEVFW0AXHud6FGwOdguDa9b5mQUBuBbVnfNPPDR5FqWwiekUgxZcN 094FJFjLe0pODu7MexiRs2vAKNUTFuRVnL30F5cOfuURVgClaiTEqJfM3vebGJ8r kEfuWYZfICz1JfoTRrYNIVhiI/1YedvbeQBay2Z88V+jmHtnkZ1kA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddtvddgleekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkffoggfgsedtkeertdertddtnecuhfhrohhmpefurghmuhgvlhcu jfholhhlrghnugcuoehsrghmuhgvlhesshhhohhllhgrnhgurdhorhhgqeenucggtffrrg htthgvrhhnpeeiteekhfehuddugfeltddufeejjeefgeevheekueffhffhjeekheeiffdt vedtveenucfkphepjedtrddufeehrddugeekrdduhedunecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepshgrmhhuvghlsehshhholhhlrghnugdr ohhrgh X-ME-Proxy: Received: from titanium.stl.sholland.net (70-135-148-151.lightspeed.stlsmo.sbcglobal.net [70.135.148.151]) by mail.messagingengine.com (Postfix) with ESMTPA id 52770240054; Sun, 18 Apr 2021 22:52:47 -0400 (EDT) From: Samuel Holland To: Maxime Ripard , Chen-Yu Tsai , Jernej Skrabec Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org, Samuel Holland Subject: [PATCH 0/2] sunxi: Enforce consistent MMC numbering Date: Sun, 18 Apr 2021 21:52:44 -0500 Message-Id: <20210419025246.21722-1-samuel@sholland.org> X-Mailer: git-send-email 2.26.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dealing with the inconsistent numbering has been a major pain, and there is a solution with (as far as I can tell) no tangible downsides. So let's use it. Yes, I know the kernel supports UUIDs for root=. But UUIDs do not help when referencing the whole, unpartitioned device, like is needed for updating the bootloader and firmware. So for the use case of "write a bootloader to the SD card, regardless of where the board is currently booted from", I know of two options: - Dig around in sysfs to find the mmc number from the MMIO address, which means I have to know the MMIO addresses for every SoC, or - Apply patches like these. Samuel Holland (2): ARM: dts: sunxi: h3/h5: Enforce consistent MMC numbering arm64: dts: allwinner: Enforce consistent MMC numbering arch/arm/boot/dts/sunxi-h3-h5.dtsi | 6 ++++++ arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 6 ++++++ arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 6 ++++++ 3 files changed, 18 insertions(+) -- 2.26.3