Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp710595pxx; Wed, 28 Oct 2020 15:12:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzjpmogTAa/jidiBdWGp1hUvaMkx5wYzG7pSUn6EPSDo93J90TIs4zFs16btU33ErWReTWh X-Received: by 2002:a50:be87:: with SMTP id b7mr1096484edk.185.1603923144417; Wed, 28 Oct 2020 15:12:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603923144; cv=none; d=google.com; s=arc-20160816; b=wTVP31ROWZf583Tx89GaLiSlIG3Qep+QnnJZmvQQatlUVQNozTisg+bm5NDSOsRdst RqbDLz25jGoP+9w9LflYMp1vBTlW+HnVnPna0dA14iNUsHtlAg/ufH3saYh1NxvmIFZU QDB8Caq2r+QHYiTzkjy2Wv7UT1ANxL+N4znEwNi+E6iuRVjJIwFvakZy1vfW8Rhge3Yy fwvPjrxrEcqsL9jrwCOnzZaNcO45VYsWvgMLwZZtGbZE5dTHFkZkolju4khB0cJ1oM2r Pd1bEKJTOCOd5J4QMh/hpaTJvhyzieWnMPYiiNw5sdVRNysHmuso3pHM8Y/GlRX1X3eW Rorw== 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=NudNzOcldIP1IfRRfm/7AjFGi+JTTIRZUKqs1VNpcVk=; b=KTMblqeUFvNzd8LxyG85dVJOskWo8Fgti157vBzemVwRbDLkeogecTrpvLMAT/E+N3 afLcvVurXOtZcEbMKGLDOHUpVWJzqFbfrkB0vz71IDGsY7tbY6QovvZ/V0ujFXSTOx+5 mhQY3XHMLcd7QASEKv6ivxzaWZCcJ0/9VfckYXXHD07+iThBBdJi+GnTTAMjllMJuDcq sKynhYft4DvX2mWb/EBys5SxXBuDPypCTEPcD/RYK6WGRlAlN1k2b62kQr9l4zZw+Bh1 tfYfQ0d22VIQ6fR+pTkjky8DUBGhg8pQ7qoNAdsw+PabMluZluPuuAXrBKJLwbcLQMXD 1RMw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v13si858522edl.492.2020.10.28.15.12.00; Wed, 28 Oct 2020 15:12:24 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730531AbgJ1WK2 convert rfc822-to-8bit (ORCPT + 99 others); Wed, 28 Oct 2020 18:10:28 -0400 Received: from mslow2.mail.gandi.net ([217.70.178.242]:40174 "EHLO mslow2.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730489AbgJ1WKT (ORCPT ); Wed, 28 Oct 2020 18:10:19 -0400 Received: from relay4-d.mail.gandi.net (unknown [217.70.183.196]) by mslow2.mail.gandi.net (Postfix) with ESMTP id 0E2B13AC1A2; Wed, 28 Oct 2020 09:49:00 +0000 (UTC) X-Originating-IP: 91.224.148.103 Received: from xps13 (unknown [91.224.148.103]) (Authenticated sender: miquel.raynal@bootlin.com) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 2CE3FE0005; Wed, 28 Oct 2020 09:48:36 +0000 (UTC) Date: Wed, 28 Oct 2020 10:48:35 +0100 From: Miquel Raynal To: Md Sadre Alam Cc: agross@kernel.org, bjorn.andersson@linaro.org, richard@nod.at, vigneshr@ti.com, robh+dt@kernel.org, linux-arm-msm@vger.kernel.org, linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, sricharan@codeaurora.org Subject: Re: [PATCH 0/5] mtd: rawnand: qcom: Add support for QSPI nand Message-ID: <20201028104835.3dc31745@xps13> In-Reply-To: <1602307902-16761-1-git-send-email-mdalam@codeaurora.org> References: <1602307902-16761-1-git-send-email-mdalam@codeaurora.org> Organization: Bootlin X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Md Sadre Alam wrote on Sat, 10 Oct 2020 11:01:37 +0530: > QPIC 2.0 supports Serial NAND support in addition to all features and > commands in QPIC 1.0 for parallel NAND. Parallel and Serial NAND cannot > operate simultaneously. QSPI nand devices will connect to QPIC IO_MACRO > block of QPIC controller. There is a separate IO_MACRO clock for IO_MACRO > block. Default IO_MACRO block divide the input clock by 4. so if IO_MACRO > input clock is 320MHz then on bus it will be 80MHz, so QSPI nand device > should also support this frequency. > > QPIC provides 4 data pins to QSPI nand. In standard SPI mode (x1 mode) data > transfer will occur on only 2 pins one pin for Serial data in and one for > serial data out. In QUAD SPI mode (x4 mode) data transfer will occur at all > the four data lines. QPIC controller supports command for x1 mode and x4 mode. > > Md Sadre Alam (5): > dt-bindings: qcom_nandc: IPQ5018 QPIC NAND documentation > mtd: rawnand: qcom: Add initial support for qspi nand > mtd: rawnand: qcom: Read QPIC version > mtd: rawnand: qcom: Enable support for erase,read & write for serial > nand. > mtd: rawnand: qcom: Add support for serial training. > > .../devicetree/bindings/mtd/qcom_nandc.txt | 3 + > drivers/mtd/nand/raw/nand_ids.c | 13 + > drivers/mtd/nand/raw/qcom_nandc.c | 502 ++++++++++++++++++++- > 3 files changed, 494 insertions(+), 24 deletions(-) > I'm sorry but this series clearly breaks the current layering. I cannot authorize SPI-NAND code to fall into the raw NAND subsystem. As both typologies cannot be used at the same time, I guess you should have another driver handling this feature under the spi/ subsystem + a few declarations in the SPI-NAND devices list. Thanks, Miquèl