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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C305EC4321E for ; Mon, 5 Dec 2022 11:31:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=KgVsoj3+qYiD5wkMg7WkNXB2ClY0ad6S4ZEp8NA0y0w=; b=BG6M4vYgJVhE+p DAJJ6AU2QEgQY4oLJEDfTVrW/hdyptSX2LDiJiDauGMQsWbYSvFVVpC2JyowNZD4XO38RJFx9UA1k icsbBZB2JMDVTUa5af947+1sZrSEEFQUyoVYygZ0zD+5qtG1cfOkRMJWs2pH5yP25/fYve+MBpiYf cK/cJFhV9uoowaT0hsRyTbDtZphwwFhUrb3WaNLmLeXd/wJEyJZqZI62X7oZ4BfebLwGUIx34GUMt yMUpcjnYavt/XOBpiOWjz039HhbaVU0JuPO0ax+FVL85YMKwjPUffyinuLCba2khMgesaxLVPvYHT A92hkXfI/XociBC0lrOg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p29g1-001hv7-SO; Mon, 05 Dec 2022 11:30:25 +0000 Received: from smtp-out-12.comm2000.it ([212.97.32.82]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p29fy-001hh8-8A; Mon, 05 Dec 2022 11:30:23 +0000 Received: from francesco-nb.int.toradex.com (31-10-206-125.static.upc.ch [31.10.206.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: francesco@dolcini.it) by smtp-out-12.comm2000.it (Postfix) with ESMTPSA id 523F6BA1E14; Mon, 5 Dec 2022 12:30:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mailserver.it; s=mailsrv; t=1670239818; bh=Kq+5kUwgPfTpYZtS89P4d7VkQaEGPlQnylqnIFbeT74=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=g/WRje8fj6jvfHuYkT8TUDWTt85/46AhNKmeCUp8nZyEtUvtKV5018Aumnm61Iv6F 4ZdTgwqueynN39EvnMzDOaDU+UvhCd5ENg5dhJKSWysFf0/OrLZkoFcEoxzv6R4NKP /tJ9SA63VGqELBmJ3M8/mRF3pHKbtEQlgqK4RikgS+JvwuYZaUDx5sSmTtbLdZhKil bbUAUhg6SyKGDLkS81DNPpNQc52uzJE0otpXUjSdXf7vt04Y98Sd5RlMDu8wGXD1Yy +hRORK7IwWExhHGCbI2RrNIue/sQhH8i5GzS9BIJjthj1FkgeLqWKfBO+p/rCCEOSC hyfYTxSo49gaw== Date: Mon, 5 Dec 2022 12:30:16 +0100 From: Francesco Dolcini To: Miquel Raynal , Marek Vasut Cc: Francesco Dolcini , Richard Weinberger , Vignesh Raghavendra , linux-mtd@lists.infradead.org, Francesco Dolcini , Shawn Guo , linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org, u-boot@lists.denx.de Subject: Re: [PATCH v1] mtd: parsers: ofpart: Fix parsing when size-cells is 0 Message-ID: References: <20221202115327.4475d3a2@xps-13> <20221202150556.14c5ae43@xps-13> <2b6fc52d-60b9-d0f4-ab91-4cf7a8095999@denx.de> <20221202160030.1b8d0b8a@xps-13> <223b7a4e-3aff-8070-7387-c77d2ded1dd6@denx.de> <20221202164904.08d750df@xps-13> <0503c46d-c385-74f5-f762-51d87a5ebaff@denx.de> <20221202174255.2c1cb2ff@xps-13> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221205_033022_458745_70DAF336 X-CRM114-Status: GOOD ( 18.44 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello Miquel On Fri, Dec 02, 2022 at 06:20:02PM +0100, Francesco Dolcini wrote: > On Fri, Dec 02, 2022 at 05:42:55PM +0100, Miquel Raynal wrote: > > Please also do it with the NAND chip described. If, when the NAND chip > > is described U-Boot tries to create partitions in the controller node, > > then the situation is even worse than I thought. But I believe > > It's like that for U-Boot older than v2022.04 ... and IMO we cannot > ignore it. > > Said that from the code U-Boot looks into a `partition{}` node only as a > direct child of the nand-controller, if there is a nand-chip in between > the nand-controller{} and the partitions{} it will just ignore it. > > I could try to see what it is doing exactly, but I would need a little > bit more time, I just tried changing the DTS as wrote I got a non > bootable system. If I have a nand-chip { partitions {} } described in the dts U-Boot (even the latest one) ignores it and generates the partition as child of the nand controller, the linux parser however see that partitions{} exists, even if empty, and ignore the partition directly defined as child of the nand controller. TL;DR: parser fails and boot fails according to that. Francesco _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel