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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0F16FC0018A for ; Fri, 3 Nov 2023 13:24:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1376334AbjKCNYX (ORCPT ); Fri, 3 Nov 2023 09:24:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40708 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229463AbjKCNYV (ORCPT ); Fri, 3 Nov 2023 09:24:21 -0400 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0066C111; Fri, 3 Nov 2023 06:24:14 -0700 (PDT) Received: from pps.filterd (m0279867.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3A3Bumsn000971; Fri, 3 Nov 2023 13:23:56 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=qcppdkim1; bh=BXRh8XjjR22c6SWsyXduhIg6ETGYP+wKqm6uE98Zfhg=; b=UWhaPc+WrKZaG0wngW56TD907NbHdKAn6A+WdpXe/KaE2p3X/KS20LOksyfpij06PpRP XuA61cchGv/qw/1HITrzaPacGoi7QpMYQsMEYLMLKWYGC1lk8quFY89+B4wrNibL0DaH F1On3sLoBqsrrcBeehjGv360IveKjyhXg+NCDbRLkYPxsaOVUasu9/mKCYp7TRZiDVqm YNcykYLjdcDqImqcXCTLdVr8uci53kq+MhsObNa6JArhpLffadFwIsOkVgTGcEF8oSv6 kISlIlKM3KoiO4FwmIc3X/4FV/LWncgw4A54feCMhdf3q/LH0RuwMsj5uwI/uFiYkE23 QA== Received: from nasanppmta03.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3u4r00h660-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 03 Nov 2023 13:23:56 +0000 Received: from nasanex01a.na.qualcomm.com (nasanex01a.na.qualcomm.com [10.52.223.231]) by NASANPPMTA03.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 3A3DNtDR020775 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 3 Nov 2023 13:23:55 GMT Received: from [10.201.203.219] (10.80.80.8) by nasanex01a.na.qualcomm.com (10.52.223.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.39; Fri, 3 Nov 2023 06:23:49 -0700 Message-ID: <4b911907-44b9-c164-9648-3d399e557672@quicinc.com> Date: Fri, 3 Nov 2023 18:53:46 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: [RFC PATCH 1/5] mtd: nand: ecc-qcom: Add support for ECC Engine Driver Content-Language: en-US To: Dmitry Baryshkov CC: Krzysztof Kozlowski , , , , , , , , , , , , , , , , , References: <20231031120307.1600689-1-quic_mdalam@quicinc.com> <20231031120307.1600689-2-quic_mdalam@quicinc.com> <553c1373-c9a0-b2af-2286-058824e31bad@quicinc.com> From: Md Sadre Alam In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nasanex01a.na.qualcomm.com (10.52.223.231) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-ORIG-GUID: yB9V2oOg36eNJzFEQMzSvY3DRh3BJmo2 X-Proofpoint-GUID: yB9V2oOg36eNJzFEQMzSvY3DRh3BJmo2 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.987,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-11-03_12,2023-11-02_03,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 adultscore=0 mlxscore=0 mlxlogscore=999 clxscore=1011 impostorscore=0 spamscore=0 bulkscore=0 priorityscore=1501 suspectscore=0 malwarescore=0 lowpriorityscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2310240000 definitions=main-2311030112 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/3/2023 6:03 PM, Dmitry Baryshkov wrote: > On Fri, 3 Nov 2023 at 14:25, Md Sadre Alam wrote: >> >> >> >> On 10/31/2023 10:41 PM, Krzysztof Kozlowski wrote: >>> On 31/10/2023 13:03, Md Sadre Alam wrote: >>> >>> Eh? Empty? >> >> QPIC controller has the ecc pipelined so will keep the ecc support >> inlined in both raw nand and serial nand driver. >> >> Droping this driver since device node was NAK-ed >> https://www.spinics.net/lists/linux-arm-msm/msg177596.html > > It seems, we have to repeat the same thing again and again: > > It was not the device node that was NAKed. It was the patch that was > NAKed. Please read the emails carefully. > > And next time please perform dtbs_check, dt_binding_check and > checkpatch before sending the patch. > > It is perfectly fine to ask questions 'like we are getting we are > getting this and that issues with the bindings, please advise'. It is > not fine to skip that step completely. Sorry in V1 will run all basic checks. Based on below feedback [1] and NAK on the device node patch got idea of having separate device node for ECC is not acceptable. Could you please help to clarify that. Since ECC block is inlined with QPIC controller so is the below device node acceptable ? bch: qpic_ecc { compatible = "qcom,ipq9574-ecc"; status = "ok"; }; [1] https://www.spinics.net/lists/linux-arm-msm/msg177525.html > >>> >>>> Signed-off-by: Md Sadre Alam >>>> Signed-off-by: Sricharan R >>>> --- >>>> drivers/mtd/nand/Kconfig | 7 ++ >>>> drivers/mtd/nand/Makefile | 1 + >>>> drivers/mtd/nand/ecc-qcom.c | 198 ++++++++++++++++++++++++++++++++++++ >>>> 3 files changed, 206 insertions(+) >>>> create mode 100644 drivers/mtd/nand/ecc-qcom.c >>>> >>> >>> ... >>> >>>> + >>>> + return 0; >>>> +} >>>> +EXPORT_SYMBOL(qcom_ecc_config); >>>> + >>>> +void qcom_ecc_enable(struct qcom_ecc *ecc) >>>> +{ >>>> + ecc->use_ecc = true; >>>> +} >>>> +EXPORT_SYMBOL(qcom_ecc_enable); >>> >>> Drop this and all other exports. Nothing here explains the need for them. >>> >>>> + >>>> +void qcom_ecc_disable(struct qcom_ecc *ecc) >>>> +{ >>>> + ecc->use_ecc = false; >>>> +} >>>> +EXPORT_SYMBOL(qcom_ecc_disable); >>>> + >>>> +static const struct of_device_id qpic_ecc_dt_match[] = { >>>> + { >>>> + .compatible = "qcom,ipq9574-ecc", >>> >>> Please run scripts/checkpatch.pl and fix reported warnings. Some >>> warnings can be ignored, but the code here looks like it needs a fix. >>> Feel free to get in touch if the warning is not clear. >>> >>> Checkpatch is preerquisite. Don't send patches which have obvious issues >>> pointed out by checkpatch. It's a waste of reviewers time. >>> >>>> + }, >>>> + {}, >>>> +}; >>>> + >>>> +static int qpic_ecc_probe(struct platform_device *pdev) >>>> +{ >>>> + struct device *dev = &pdev->dev; >>>> + struct qpic_ecc *ecc; >>>> + u32 max_eccdata_size; >>>> + >>>> + ecc = devm_kzalloc(dev, sizeof(*ecc), GFP_KERNEL); >>>> + if (!ecc) >>>> + return -ENOMEM; >>>> + >>>> + ecc->caps = of_device_get_match_data(dev); >>>> + >>>> + ecc->dev = dev; >>>> + platform_set_drvdata(pdev, ecc); >>>> + dev_info(dev, "probed\n"); >>> >>> No, no such messages. >>> >>> >>> >>> Best regards, >>> Krzysztof >>> > > >