From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bean Huo Subject: Re: [PATCH v1 1/3] mtd: physmap: add dual die entry in devicetree binding Date: Fri, 23 Feb 2018 11:07:17 +0000 Message-ID: References: <1519241514-6466-1-git-send-email-beanhuo@outlook.com> , <20180222140542.47340842@bbrezillon> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180222140542.47340842@bbrezillon> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-mtd" Errors-To: linux-mtd-bounces+gldm-linux-mtd-36=gmane.org@lists.infradead.org To: Boris Brezillon Cc: "mark.rutland@arm.com" , "devicetree@vger.kernel.org" , "boris.brezillon@free-electrons.com" , "richard@nod.at" , "marek.vasut@gmail.com" , "robh+dt@kernel.org" , "linux-mtd@lists.infradead.org" , "cyrille.pitchen@wedev4u.fr" , "computersforpeace@gmail.com" , "dwmw2@infradead.org" , beanhuo List-Id: devicetree@vger.kernel.org Boris, thanks for the review. >> + - dual-die-stack: boolean to enable support for the devices with the >> + two dies in stack. >How about making that more future proof and adding a property that >directly contains the number of dies (num-dies)? Exactly, I also thought here should add a property, through which it can be compatible with all kinds of PNOR for the future more dies stacked device. But currently, it doesn't exist PNOR device with more than two dies, and we have no idea about 4/6 dies stacked device operation sequence. so I simply add a boolean entry and try to only enable dual-die stacked PNOR firstly. Maybe I can try to do that in next version patch. the software implementation is so flexible. >> >> For JEDEC compatible devices, the following additional properties >> are defined: ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oln040092000013.outbound.protection.outlook.com ([40.92.0.13] helo=NAM01-BN3-obe.outbound.protection.outlook.com) by bombadil.infradead.org with esmtps (Exim 4.89 #1 (Red Hat Linux)) id 1epBCN-0007c7-6A for linux-mtd@lists.infradead.org; Fri, 23 Feb 2018 11:07:32 +0000 From: Bean Huo To: Boris Brezillon CC: "dwmw2@infradead.org" , "computersforpeace@gmail.com" , "marek.vasut@gmail.com" , "richard@nod.at" , "cyrille.pitchen@wedev4u.fr" , "robh+dt@kernel.org" , "mark.rutland@arm.com" , "linux-mtd@lists.infradead.org" , "devicetree@vger.kernel.org" , beanhuo , "boris.brezillon@free-electrons.com" Subject: Re: [PATCH v1 1/3] mtd: physmap: add dual die entry in devicetree binding Date: Fri, 23 Feb 2018 11:07:17 +0000 Message-ID: References: <1519241514-6466-1-git-send-email-beanhuo@outlook.com> , <20180222140542.47340842@bbrezillon> In-Reply-To: <20180222140542.47340842@bbrezillon> Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Boris,=0A= thanks for the review.=0A= =0A= >> + - dual-die-stack: boolean to enable support for the devices with the= =0A= >> + two dies in stack.=0A= =0A= >How about making that more future proof and adding a property that=0A= >directly contains the number of dies (num-dies)?=0A= =0A= Exactly, I also thought here should add a property, through which it can be= compatible=0A= with all kinds of PNOR for the future more dies stacked device.=0A= But currently, it doesn't exist PNOR device with more than two dies, and w= e=0A= have no idea about 4/6 dies stacked device operation sequence. so I simply = add a boolean=0A= entry and try to only enable dual-die stacked PNOR firstly.=0A= =0A= Maybe I can try to do that in next version patch. the software implementati= on is so flexible.=0A= =0A= >>=0A= >> For JEDEC compatible devices, the following additional properties=0A= >> are defined:=0A= =0A=