Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3118252pxk; Mon, 28 Sep 2020 08:46:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwWFu94Amr3XfRTvayzwpotgPX5ALe/zuAqO3xKWOv7UdrwbxuLAxztx6iudYizBX8a0Fo5 X-Received: by 2002:a17:906:e88:: with SMTP id p8mr2423009ejf.134.1601308003277; Mon, 28 Sep 2020 08:46:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601308003; cv=none; d=google.com; s=arc-20160816; b=LZ2A8k+wKY4W/SPi3PKuXPBXojn1apZFvkGEpMda8ldOpwbzBnDrtCRcOY3unllAjP FAnEU7qcdP/n4troi82wvhdSiYgDSeNANn9tjeSr05jbewFGI589UP9JwdAL3+my4S7Y FA0L5mHloc3o0cxZkypLN5l7uZthd5ok5vezaEP4Tup6C689jo0J46YsV9nvW5jKzfCu BblAT7pwIy8RypU41cuEBtIJEFFOOysZoB5dk+orgrLdXXUXmdv7Z1eWPIqrAwz2OpLS tGxnOaVVifcXs3sdxAGMI2dHl0UtOGO40/25hBL/g7iugPIl9zl7B15XB3WwhRiMOzsI f2vg== 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 :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=eOSgWLzTxLQngE26Ck7IGm1KTyUAfoA2BFCpj9C47PE=; b=s4BOQBwUZXR7Zls54CPtWlmJZRH/yW7UWXoo7SbiEtqdF4acN3rtHK8GDIVB/wqtn8 4WvQnAZeelue7ru1zh34GhEPK7arirn227Q1G6zGNG0Zcs8JnGxytLHVI6hEuNSK6G1z rS5A36s3VPZqy0oVaE+ZRDlxgnkXBfRZdFn3wvEIo9z5yvoFOrE7iPfQ67me1ovIG8/N Kncl0YdXw3subDEAbCb+cSptH7qn6ltIIcv9UxyOqQpd7sm/GL9O/12yBRNWkyM7hazH 4MLtUbwych1geu1RBGvwOCYssjKk+a9IqatVNEkHBHQ1Fm6iCX0a5SUSacQxGbrNQ0jq tBgw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y25si821952edt.563.2020.09.28.08.46.20; Mon, 28 Sep 2020 08:46:43 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726613AbgI1PpK (ORCPT + 99 others); Mon, 28 Sep 2020 11:45:10 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:48902 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726497AbgI1PpK (ORCPT ); Mon, 28 Sep 2020 11:45:10 -0400 Received: from localhost (unknown [IPv6:2a01:e0a:2c:6930:5cf4:84a1:2763:fe0d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: bbrezillon) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 9DE0C29AA6C; Mon, 28 Sep 2020 16:45:08 +0100 (BST) Date: Mon, 28 Sep 2020 17:45:05 +0200 From: Boris Brezillon To: Miquel Raynal Cc: Thirumalesha N , Richard Weinberger , Vignesh Raghavendra , Shivamurthy Shastri , Chuanhong Guo , linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 1/2] mtd: spinand: micron: Generalize the function and structure names Message-ID: <20200928174505.75fda272@collabora.com> In-Reply-To: <20200928165528.54e5db6e@xps13> References: <20200913161533.10655-1-nthirumalesha7@gmail.com> <20200913161533.10655-2-nthirumalesha7@gmail.com> <20200915101321.1afa5033@xps13> <20200928165528.54e5db6e@xps13> Organization: Collabora X-Mailer: Claws Mail 3.17.6 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 28 Sep 2020 16:55:28 +0200 Miquel Raynal wrote: > > IMHO, grouped means, ecc bytes are at continuous address, where as > > interleaved means ecc bytes splitted into multiple addresses > > I don't like the name. Interleaved means that there are OOB bytes > stored in the data section, which is not the case here. Well, I would argue that the term interleaved alone doesn't say anything about the things that are interleaved. But I guess split/grouped would be fine too if you want to avoid re-using interleaved here. > The way OOB > bytes are organized do not seem relevant to me, I think i prefer the > "_4_/_8_" naming,even if it's not very explicit. The ECC strength doesn't say anything about the scheme used for ECC bytes placement, and you might end up with 2 different schemes providing the same strength, or the same scheme used for 2 different strengths.