Message ID | 20240215134856.1313239-1-quic_mdalam@quicinc.com |
---|---|
Headers |
Return-Path: <linux-kernel+bounces-67019-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:b825:b0:106:860b:bbdd with SMTP id da37csp411124dyb; Thu, 15 Feb 2024 05:53:17 -0800 (PST) X-Forwarded-Encrypted: i=3; AJvYcCUmHJmCAZyiKVZJXs08f78BDVB7m8cFTrHrJZ5EXnbFnEX77/k+/+6zB5xthLuLu0MCS26ePFndD83+snRe4O3OfNcY7g== X-Google-Smtp-Source: AGHT+IFS2/6uaGfU4cfRIqSTqw/ydgD3asYQgDrI8wI9nvne7o5/II/i2BmyyckTgKROBZdYIYfT X-Received: by 2002:a05:6214:4407:b0:68c:8874:59e9 with SMTP id oj7-20020a056214440700b0068c887459e9mr1817473qvb.43.1708005197196; Thu, 15 Feb 2024 05:53:17 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1708005197; cv=pass; d=google.com; s=arc-20160816; b=qfJbTzDiKgIFObYPF0ZWvzD4z7ypz493w67Y2UISdNZ4NPAoZiNF59KsG5hEYAs7Lq Asp/jwLSLDWgdq8rNgdBTLy68W4Vs8LEXF02okVPtHaDOaFoaqvaxcx8jIJX2RQWStgD tgQwK1rNZfv7cAtt4pr5I2wOHpxVCys+DShIkaAvFSYwT5thQDPR4Le7/k8B7yymsRRL /PGuANQVU6sDIhg9P7NeD/EL0AcwVfbql2jJkclJcNWwhFsoIfGan/v9VIuUuZRiLkdb DZ1UT3I8qcfXg0b9U4WBcDTo0Esj4ilEBmygzb4fWXtCjzxGWy01MfgUWw+kNHliCgQP +sHA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=RcrWZqECuZv3JnbHoWbT66Q4is1ZH+pdI5bP3PIcij0=; fh=Rprd2jVbPlcdx3hC2MHWc25e+a9rL0c9TQSQaoi1pRQ=; b=LfQvGOur3XS9OCQhi5HlUzCFrQ3b9wIQ7YXOkNA/rb9TEwPtr8/DLzv6vCaOvElJj5 ZLdZok8rROeL6YWL76L9Z1gOJxXDCxRc9vY5dqrMqTDAsPz6hoUSRhQuurf6j+XG6gu4 87s5BOoF7wNzRbpxK384Y4XDAiH4mcmbDy6LPrahDhOjoRLvP53z5jhsoXHr7WEzuN0y UO9QyEpRm/OxFckCxHbnTM25Rrp4t2VS2x0SvNgJ1Y0OTbSkptVTNMNj59yF7V+9hR0c BNJk0eDd+IjodIg78Ctus7uTZf5nThQiIrh4J7pQNf5cQaQJTmxRXICy9Lf0JEn1TZ/N d2Cg==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b="WA5t/Qpx"; arc=pass (i=1 spf=pass spfdomain=qualcomm.com dkim=pass dkdomain=quicinc.com dmarc=pass fromdomain=quicinc.com); spf=pass (google.com: domain of linux-kernel+bounces-67019-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-67019-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id 3-20020a056214202300b0068cd7c873e4si1538431qvf.511.2024.02.15.05.53.17 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 15 Feb 2024 05:53:17 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-67019-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b="WA5t/Qpx"; arc=pass (i=1 spf=pass spfdomain=qualcomm.com dkim=pass dkdomain=quicinc.com dmarc=pass fromdomain=quicinc.com); spf=pass (google.com: domain of linux-kernel+bounces-67019-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-67019-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quicinc.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 01C3A1C20F3A for <ouuuleilei@gmail.com>; Thu, 15 Feb 2024 13:53:17 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id BBB52132C35; Thu, 15 Feb 2024 13:49:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=quicinc.com header.i=@quicinc.com header.b="WA5t/Qpx" Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3620412FF72; Thu, 15 Feb 2024 13:49:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708004977; cv=none; b=P5RYaNXuyEZsQWG55Val+s6B54u6Li6/zpz2oG4CuLRx7JCEAAhvRxbyvPrlu3mN/DkIQIQnJ8d0FhHJA0d/CU5KC2nOQoOoEO5IAxyMZ6dsvOKBtiQ3FRnklEe+rjk3ENBwsC92RpbuGN2OH2NmK/8kDAWiFz1dXHyezcZKFUw= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1708004977; c=relaxed/simple; bh=vswra8flRKF1aZxWHZnwl+kY9wTzxTZmzikmYi/UtuA=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=i0Pp3BRTctmNxs6dRwe6TSnvfzTCConxh/pEjBDs5Pn/9o80rJszWEdqzoZ0OlsWtos8vjFJl+B5FKzrx8oUrb9hxlT6v6bclZWyIYTBnnHQkTtAyCRLsCrQ/xA7qg9bRfsFFzCWU7r5szyi2g+zvEWtFthby+uw6bMIg9YWqOc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=quicinc.com; spf=pass smtp.mailfrom=qualcomm.com; dkim=pass (2048-bit key) header.d=quicinc.com header.i=@quicinc.com header.b=WA5t/Qpx; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=quicinc.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=qualcomm.com Received: from pps.filterd (m0279863.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.24/8.17.1.24) with ESMTP id 41FAITGq004803; Thu, 15 Feb 2024 13:49:12 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=qcppdkim1; bh=RcrWZqECuZv3JnbHoWbT 66Q4is1ZH+pdI5bP3PIcij0=; b=WA5t/QpxKOe2Om+EHXKaqL+uFjTUnot1m7rB VEqExolW+bt9jECrlrSKDfheCqq9EksOVuJjL3m33XPGj4CZbNaprnWpN1tWwxOM MEdyVkjWsZ+LK8eUeBy/vF+xcW5srRXP3goZLUvmOy6bmASo6vVQDN/xaPfhsuDi k1/I3wkDnVpZjRD6fYqwwoDg+L1LNJeZS2LENmsYJsE+vWqS4dJXVv2bAxmCoWur kn6Z/0cs/bONFP7WezkeqyC9frXi28LIunXFzq5aCR1PSKe2QIN9ZDV/X47i8nAJ pvJEtWzTu/iDyauR4NXCNfB8Hr1TO3roXSCWtyjAzPv2YkWtIA== Received: from apblrppmta01.qualcomm.com (blr-bdr-fw-01_GlobalNAT_AllZones-Outside.qualcomm.com [103.229.18.19]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3w96c3snrj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Feb 2024 13:49:12 +0000 (GMT) Received: from pps.filterd (APBLRPPMTA01.qualcomm.com [127.0.0.1]) by APBLRPPMTA01.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTP id 41FDn8Zt009961; Thu, 15 Feb 2024 13:49:08 GMT Received: from pps.reinject (localhost [127.0.0.1]) by APBLRPPMTA01.qualcomm.com (PPS) with ESMTPS id 3w627mb92b-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Feb 2024 13:49:08 +0000 Received: from APBLRPPMTA01.qualcomm.com (APBLRPPMTA01.qualcomm.com [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 41FDn8J5009930; Thu, 15 Feb 2024 13:49:08 GMT Received: from hu-devc-blr-u22-a.qualcomm.com (hu-mdalam-blr.qualcomm.com [10.131.36.157]) by APBLRPPMTA01.qualcomm.com (PPS) with ESMTPS id 41FDn8K9009925 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Feb 2024 13:49:08 +0000 Received: by hu-devc-blr-u22-a.qualcomm.com (Postfix, from userid 466583) id 5DAA441254; Thu, 15 Feb 2024 19:19:07 +0530 (+0530) From: Md Sadre Alam <quic_mdalam@quicinc.com> To: andersson@kernel.org, konrad.dybcio@linaro.org, broonie@kernel.org, robh@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com, manivannan.sadhasivam@linaro.org, linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org Cc: quic_srichara@quicinc.com, quic_varada@quicinc.com, quic_mdalam@quicinc.com Subject: [PATCH 0/5] Add QPIC SPI NAND driver Date: Thu, 15 Feb 2024 19:18:51 +0530 Message-Id: <20240215134856.1313239-1-quic_mdalam@quicinc.com> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-QCInternal: smtphost X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-ORIG-GUID: Ek8biRZv5ykBYakJkOmo1PCtQqOcYkam X-Proofpoint-GUID: Ek8biRZv5ykBYakJkOmo1PCtQqOcYkam X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1011,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2024-02-15_12,2024-02-14_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 bulkscore=0 suspectscore=0 impostorscore=0 adultscore=0 mlxscore=0 mlxlogscore=862 malwarescore=0 spamscore=0 lowpriorityscore=0 priorityscore=1501 phishscore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2401310000 definitions=main-2402150111 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1790973257529195659 X-GMAIL-MSGID: 1790973257529195659 |
Series | Add QPIC SPI NAND driver | |
Message
Md Sadre Alam
Feb. 15, 2024, 1:48 p.m. UTC
This series of patches will add initial supports for QPIC SPI NAND driver. Currently this driver support following commands -- RESET -- READ ID -- BLOCK ERASE -- PAGE READ -- PAGE WRITE -- GET FEATURE -- SET FEATURE -- BAD BLOCK CHECK This driver has been tested with dd command with read/write page with multiple file size 1MiB, 10MiB,40MiB etc. Also tested with "mtd" command like mtd erase, mtd write, mtd verify etc. Need help to test these all patches on SDX65 and SDX75 platform. Md Sadre Alam (5): spi: dt-bindings: add binding doc for spi-qpic-snand drivers: mtd: nand: Add qpic_common API file spi: spi-qpic: Add qpic spi nand driver support arm64: dts: qcom: ipq9574: Add SPI nand support arm64: dts: qcom: ipq9574: Disable eMMC node .../bindings/spi/qcom,spi-qpic-snand.yaml | 82 ++ .../boot/dts/qcom/ipq9574-rdp-common.dtsi | 43 + arch/arm64/boot/dts/qcom/ipq9574-rdp433.dts | 2 +- arch/arm64/boot/dts/qcom/ipq9574.dtsi | 27 + drivers/mtd/nand/Makefile | 1 + drivers/mtd/nand/qpic_common.c | 794 +++++++++++ drivers/mtd/nand/raw/qcom_nandc.c | 1226 +---------------- drivers/spi/Kconfig | 9 + drivers/spi/Makefile | 1 + drivers/spi/spi-qpic-snand.c | 1025 ++++++++++++++ include/linux/mtd/nand-qpic-common.h | 548 ++++++++ 11 files changed, 2547 insertions(+), 1211 deletions(-) create mode 100644 Documentation/devicetree/bindings/spi/qcom,spi-qpic-snand.yaml create mode 100644 drivers/mtd/nand/qpic_common.c create mode 100644 drivers/spi/spi-qpic-snand.c create mode 100644 include/linux/mtd/nand-qpic-common.h
Comments
On Thu, Feb 15, 2024 at 07:18:51PM +0530, Md Sadre Alam wrote: > This series of patches will add initial supports > for QPIC SPI NAND driver. > > Currently this driver support following commands > > -- RESET > -- READ ID > -- BLOCK ERASE > -- PAGE READ > -- PAGE WRITE > -- GET FEATURE > -- SET FEATURE > -- BAD BLOCK CHECK > > This driver has been tested with dd command with read/write page > with multiple file size 1MiB, 10MiB,40MiB etc. > Also tested with "mtd" command like mtd erase, mtd write, mtd verify etc. > This is not the first version isn't it? Where is the changelog describing what has changed since then? - Mani > Need help to test these all patches on SDX65 and SDX75 platform. > > Md Sadre Alam (5): > spi: dt-bindings: add binding doc for spi-qpic-snand > drivers: mtd: nand: Add qpic_common API file > spi: spi-qpic: Add qpic spi nand driver support > arm64: dts: qcom: ipq9574: Add SPI nand support > arm64: dts: qcom: ipq9574: Disable eMMC node > > .../bindings/spi/qcom,spi-qpic-snand.yaml | 82 ++ > .../boot/dts/qcom/ipq9574-rdp-common.dtsi | 43 + > arch/arm64/boot/dts/qcom/ipq9574-rdp433.dts | 2 +- > arch/arm64/boot/dts/qcom/ipq9574.dtsi | 27 + > drivers/mtd/nand/Makefile | 1 + > drivers/mtd/nand/qpic_common.c | 794 +++++++++++ > drivers/mtd/nand/raw/qcom_nandc.c | 1226 +---------------- > drivers/spi/Kconfig | 9 + > drivers/spi/Makefile | 1 + > drivers/spi/spi-qpic-snand.c | 1025 ++++++++++++++ > include/linux/mtd/nand-qpic-common.h | 548 ++++++++ > 11 files changed, 2547 insertions(+), 1211 deletions(-) > create mode 100644 Documentation/devicetree/bindings/spi/qcom,spi-qpic-snand.yaml > create mode 100644 drivers/mtd/nand/qpic_common.c > create mode 100644 drivers/spi/spi-qpic-snand.c > create mode 100644 include/linux/mtd/nand-qpic-common.h > > -- > 2.34.1 >
On 2/19/2024 6:34 PM, Manivannan Sadhasivam wrote: > On Thu, Feb 15, 2024 at 07:18:51PM +0530, Md Sadre Alam wrote: >> This series of patches will add initial supports >> for QPIC SPI NAND driver. >> >> Currently this driver support following commands >> >> -- RESET >> -- READ ID >> -- BLOCK ERASE >> -- PAGE READ >> -- PAGE WRITE >> -- GET FEATURE >> -- SET FEATURE >> -- BAD BLOCK CHECK >> >> This driver has been tested with dd command with read/write page >> with multiple file size 1MiB, 10MiB,40MiB etc. >> Also tested with "mtd" command like mtd erase, mtd write, mtd verify etc. >> > > This is not the first version isn't it? Where is the changelog describing what > has changed since then? The earlier patch was the RFC for design review only. > > - Mani > >> Need help to test these all patches on SDX65 and SDX75 platform. >> >> Md Sadre Alam (5): >> spi: dt-bindings: add binding doc for spi-qpic-snand >> drivers: mtd: nand: Add qpic_common API file >> spi: spi-qpic: Add qpic spi nand driver support >> arm64: dts: qcom: ipq9574: Add SPI nand support >> arm64: dts: qcom: ipq9574: Disable eMMC node >> >> .../bindings/spi/qcom,spi-qpic-snand.yaml | 82 ++ >> .../boot/dts/qcom/ipq9574-rdp-common.dtsi | 43 + >> arch/arm64/boot/dts/qcom/ipq9574-rdp433.dts | 2 +- >> arch/arm64/boot/dts/qcom/ipq9574.dtsi | 27 + >> drivers/mtd/nand/Makefile | 1 + >> drivers/mtd/nand/qpic_common.c | 794 +++++++++++ >> drivers/mtd/nand/raw/qcom_nandc.c | 1226 +---------------- >> drivers/spi/Kconfig | 9 + >> drivers/spi/Makefile | 1 + >> drivers/spi/spi-qpic-snand.c | 1025 ++++++++++++++ >> include/linux/mtd/nand-qpic-common.h | 548 ++++++++ >> 11 files changed, 2547 insertions(+), 1211 deletions(-) >> create mode 100644 Documentation/devicetree/bindings/spi/qcom,spi-qpic-snand.yaml >> create mode 100644 drivers/mtd/nand/qpic_common.c >> create mode 100644 drivers/spi/spi-qpic-snand.c >> create mode 100644 include/linux/mtd/nand-qpic-common.h >> >> -- >> 2.34.1 >> >
On 20/02/2024 12:32, Md Sadre Alam wrote: > > > On 2/19/2024 6:34 PM, Manivannan Sadhasivam wrote: >> On Thu, Feb 15, 2024 at 07:18:51PM +0530, Md Sadre Alam wrote: >>> This series of patches will add initial supports >>> for QPIC SPI NAND driver. >>> >>> Currently this driver support following commands >>> >>> -- RESET >>> -- READ ID >>> -- BLOCK ERASE >>> -- PAGE READ >>> -- PAGE WRITE >>> -- GET FEATURE >>> -- SET FEATURE >>> -- BAD BLOCK CHECK >>> >>> This driver has been tested with dd command with read/write page >>> with multiple file size 1MiB, 10MiB,40MiB etc. >>> Also tested with "mtd" command like mtd erase, mtd write, mtd verify etc. >>> >> >> This is not the first version isn't it? Where is the changelog describing what >> has changed since then? > > The earlier patch was the RFC for design review only. RFC is state of patch, not version. This is v2 then. These RFC postings are really becoming mess. Some people make multiple RFCs and then post v1 hiding entire previous history... And why even bother with calling it RFC? Best regards, Krzysztof
On 2/20/2024 5:06 PM, Krzysztof Kozlowski wrote: > On 20/02/2024 12:32, Md Sadre Alam wrote: >> >> >> On 2/19/2024 6:34 PM, Manivannan Sadhasivam wrote: >>> On Thu, Feb 15, 2024 at 07:18:51PM +0530, Md Sadre Alam wrote: >>>> This series of patches will add initial supports >>>> for QPIC SPI NAND driver. >>>> >>>> Currently this driver support following commands >>>> >>>> -- RESET >>>> -- READ ID >>>> -- BLOCK ERASE >>>> -- PAGE READ >>>> -- PAGE WRITE >>>> -- GET FEATURE >>>> -- SET FEATURE >>>> -- BAD BLOCK CHECK >>>> >>>> This driver has been tested with dd command with read/write page >>>> with multiple file size 1MiB, 10MiB,40MiB etc. >>>> Also tested with "mtd" command like mtd erase, mtd write, mtd verify etc. >>>> >>> >>> This is not the first version isn't it? Where is the changelog describing what >>> has changed since then? >> >> The earlier patch was the RFC for design review only. > > RFC is state of patch, not version. This is v2 then. > > These RFC postings are really becoming mess. Some people make multiple > RFCs and then post v1 hiding entire previous history... And why even > bother with calling it RFC? Sorry, I was not aware of this. Shall I post the next one as V3 and add references to the RFC patch and this patch in the cover letter of V3? > > Best regards, > Krzysztof >
On 21/02/2024 11:34, Md Sadre Alam wrote: > > > On 2/20/2024 5:06 PM, Krzysztof Kozlowski wrote: >> On 20/02/2024 12:32, Md Sadre Alam wrote: >>> >>> >>> On 2/19/2024 6:34 PM, Manivannan Sadhasivam wrote: >>>> On Thu, Feb 15, 2024 at 07:18:51PM +0530, Md Sadre Alam wrote: >>>>> This series of patches will add initial supports >>>>> for QPIC SPI NAND driver. >>>>> >>>>> Currently this driver support following commands >>>>> >>>>> -- RESET >>>>> -- READ ID >>>>> -- BLOCK ERASE >>>>> -- PAGE READ >>>>> -- PAGE WRITE >>>>> -- GET FEATURE >>>>> -- SET FEATURE >>>>> -- BAD BLOCK CHECK >>>>> >>>>> This driver has been tested with dd command with read/write page >>>>> with multiple file size 1MiB, 10MiB,40MiB etc. >>>>> Also tested with "mtd" command like mtd erase, mtd write, mtd verify etc. >>>>> >>>> >>>> This is not the first version isn't it? Where is the changelog describing what >>>> has changed since then? >>> >>> The earlier patch was the RFC for design review only. >> >> RFC is state of patch, not version. This is v2 then. >> >> These RFC postings are really becoming mess. Some people make multiple >> RFCs and then post v1 hiding entire previous history... And why even >> bother with calling it RFC? > > Sorry, I was not aware of this. Shall I post the next one as V3 > and add references to the RFC patch and this patch in the cover > letter of V3? Yes, like with every posting. Best regards, Krzysztof
On 2/21/2024 4:31 PM, Krzysztof Kozlowski wrote: > On 21/02/2024 11:34, Md Sadre Alam wrote: >> >> >> On 2/20/2024 5:06 PM, Krzysztof Kozlowski wrote: >>> On 20/02/2024 12:32, Md Sadre Alam wrote: >>>> >>>> >>>> On 2/19/2024 6:34 PM, Manivannan Sadhasivam wrote: >>>>> On Thu, Feb 15, 2024 at 07:18:51PM +0530, Md Sadre Alam wrote: >>>>>> This series of patches will add initial supports >>>>>> for QPIC SPI NAND driver. >>>>>> >>>>>> Currently this driver support following commands >>>>>> >>>>>> -- RESET >>>>>> -- READ ID >>>>>> -- BLOCK ERASE >>>>>> -- PAGE READ >>>>>> -- PAGE WRITE >>>>>> -- GET FEATURE >>>>>> -- SET FEATURE >>>>>> -- BAD BLOCK CHECK >>>>>> >>>>>> This driver has been tested with dd command with read/write page >>>>>> with multiple file size 1MiB, 10MiB,40MiB etc. >>>>>> Also tested with "mtd" command like mtd erase, mtd write, mtd verify etc. >>>>>> >>>>> >>>>> This is not the first version isn't it? Where is the changelog describing what >>>>> has changed since then? >>>> >>>> The earlier patch was the RFC for design review only. >>> >>> RFC is state of patch, not version. This is v2 then. >>> >>> These RFC postings are really becoming mess. Some people make multiple >>> RFCs and then post v1 hiding entire previous history... And why even >>> bother with calling it RFC? >> >> Sorry, I was not aware of this. Shall I post the next one as V3 >> and add references to the RFC patch and this patch in the cover >> letter of V3? > > Yes, like with every posting. Thank you. > > Best regards, > Krzysztof >