Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp40160pxu; Tue, 24 Nov 2020 17:56:22 -0800 (PST) X-Google-Smtp-Source: ABdhPJyzAYR7r9De1ZTkqeVWzmdnI3+y3iX7B3tvtEqrE8HEO98BDs19e4S1PxosvvL3b6ajMGxK X-Received: by 2002:a17:906:82d9:: with SMTP id a25mr1215112ejy.101.1606269381951; Tue, 24 Nov 2020 17:56:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606269381; cv=none; d=google.com; s=arc-20160816; b=vioOFWMbCYOwViLY3FklrUIehhpjHx7Hm038TzA7h0hLZNcPY1BaKERcmLNXAo47Vb XbIUQvCMPeGhmKuSpQB24aEcYzRxhkrMAR2qMH8Up7J7vr1M1Fn8vbshIe04UZcWNGje NoWqiiNZmoHUqUOKoM/i/+Ddgqfv9dJ8ANwFVoctUwSqaTI4jW7L1f03hxJholmOkCA3 Ffs8C7VcZmuI7MmzlpwJx3IRIJTjDYRAxY/gg+PDFsl+YGf+9334UTv/ME3smQSAzLkp LRwCm29LGXrn2zvOoHXbnH0S/xd1SOLDzW91OaDTT2XdRmtlxc+KO+9ucUaSDBHTfmO1 uODA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:user-agent:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version :dkim-signature; bh=1LdtFZjQj4nJpth6euyR4ivHCTaufrYR8pun171sr7w=; b=kEnAKYmqP6xjGJfAtWxhQR6z74e50tRhbFne6Mwf9Dwd9+T5Qi3YjeYjZ4ud8RS8TT ak1f0lOASd8L89qZNXNFkQmBmVV9L8x0b0YSmzH/maWQTY3xPchSLUzjwBQVkoobwDHE f7JuUS7YcJvkrs10JR9butW7+hzUXVqfRsYoxm56AdY5ba34jrsFlaRte++GbfUjv+oO gdNbnvnQHaYLdVmkPhzHypoYikIWJEpVHMiHzmKZGOFS3GGjBQyUoAI8qRkKuYtUKacy V3jPGuGZGMH94mGQNKgMydWBO7R5nr0LSh2Yustj4fNZZMjnH2YemfuVi6s+4WGsdcRx QbDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b=I5BI7ZEE; 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 rn28si414471ejb.585.2020.11.24.17.55.59; Tue, 24 Nov 2020 17:56:21 -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; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b=I5BI7ZEE; 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 S1730392AbgKXIDP (ORCPT + 99 others); Tue, 24 Nov 2020 03:03:15 -0500 Received: from ssl.serverraum.org ([176.9.125.105]:37159 "EHLO ssl.serverraum.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725497AbgKXIDK (ORCPT ); Tue, 24 Nov 2020 03:03:10 -0500 Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 3BE4023E45; Tue, 24 Nov 2020 09:03:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1606204984; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1LdtFZjQj4nJpth6euyR4ivHCTaufrYR8pun171sr7w=; b=I5BI7ZEEc+PUzGevx0oD5I1fnLHp80tmJwQ0q5EqY8wDjtqtKnVxBt84fPY3FhXAzNtXaI oaxL+C3qzPZxEW27CMq7QIkUcCh5251ehDHM29RFxQqDdHB0xV4ZDHI4RgXi/CcUUjK1aj gnrPugYfQDaj4T+ZFXCmkjAba7f9yXM= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 24 Nov 2020 09:03:00 +0100 From: Michael Walle To: "Y.b. Lu" Cc: Vladimir Oltean , Shawn Guo , Leo Li , Rob Herring , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Adrian Hunter , Ulf Hansson , linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, Ashish Kumar Subject: Re: [PATCH] arm64: dts: ls1028a: make the eMMC and SD card controllers use fixed indices In-Reply-To: References: <20201119155025.965941-1-vladimir.oltean@nxp.com> <20201120093015.duel3yx63cbya77w@skbuf> User-Agent: Roundcube Webmail/1.4.9 Message-ID: <71a86b0fbc95892f8fd240e0919e7e23@walle.cc> X-Sender: michael@walle.cc Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 2020-11-24 08:41, schrieb Y.b. Lu: > Hi Vladimir, > >> -----Original Message----- >> From: Vladimir Oltean >> Sent: Friday, November 20, 2020 5:30 PM >> To: Y.b. Lu >> Cc: Shawn Guo ; Leo Li ; Rob >> Herring ; linux-arm-kernel@lists.infradead.org; >> devicetree@vger.kernel.org; Adrian Hunter ; >> Ulf >> Hansson ; linux-mmc@vger.kernel.org; >> linux-kernel@vger.kernel.org; Ashish Kumar ; >> Michael Walle >> Subject: Re: [PATCH] arm64: dts: ls1028a: make the eMMC and SD card >> controllers use fixed indices >> >> On Fri, Nov 20, 2020 at 02:04:02AM +0000, Y.b. Lu wrote: >> > Hi Vladimir, >> > >> > I have already upstreamed a patch for all affected layerscape boards. >> > >> https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/commit/? >> h=imx/dt64&id=342ab37ecaf8c1b10dd3ca9a1271db29a6af0705 >> > >> > Please check whether it works for you. >> >> Thanks, one can tell that I haven't done my due diligence of checking >> Shawn's tree first. I'll cherry-pick that patch and carry on with my >> work. >> >> However, the fact still remains that Michael has expressed his opinion >> regarding mmcblk0 vs mmcblk1. Do you think that we could make the >> aliases a per-board option instead of per-SoC? Consider that there >> might >> even be boards that only use SD card. It would be strange for the >> block >> device in that case to be called /dev/mmcblk1. > > I don't think it's a problem in board dts to define board specific > thing, like re-defining alias, and disabling any IP it not using. First, why would you put it in the architecture include anyway? That is really board-specific. That is like you would say, we enable all devices and a board could potentially disable it. TBH it seems that this will fit your reference boards and you don't care about the other ones which uses that include. And as Vladimir pointed out, what do you do if you just have the eMMC on the LS1028A. It will be mmcblk1 unless you do something like the following in the board dts: mmc0 = &esdhc; /delete-property/ mmc1; That is really cumbersome, isnt it? -michael