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 X-Spam-Level: X-Spam-Status: No, score=-8.5 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,T_DKIMWL_WL_HIGH,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E70EBC28EBD for ; Sun, 9 Jun 2019 21:10:35 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BD9F4206BB for ; Sun, 9 Jun 2019 21:10:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="mWk7L73I"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="yXim0t1z" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BD9F4206BB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=dnqJ0kLPaPbYqLIDHFHjkx7ChZ0eWmy3JyUD38Cpqog=; b=mWk7L73IQdHugs ypsMeycCHLEmriXns0JS/IyojUKusYAGT9wTBeRGR/HeW9W1rIhDbOZu6h3htYA/qxUro5ZvX1pnZ MSw+Xr4fd6mAGc/SEhVKuapzQ6MYnn0xs0U6ZL9N26TWdHC3WT238ONOsINveru1TMhqn3dhfpVWE f7zYqvBbeAIu2gugCox0cxfUL+MRntge15khVB8kSHBQac9eoQx1Egpy52mB+tPdDkuBw5F3BCmge R+k0+eF4oxVL6Csa3YXSfO2YkfJnCn0zsw9S2KVxN+Lgc14qqItQOiThZsuu9l61r+9fpP/qvkCgZ uW86brBcAgksoUApbQeA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1ha55G-0001nW-E6; Sun, 09 Jun 2019 21:10:34 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1ha55D-0001nC-8W for linux-arm-kernel@lists.infradead.org; Sun, 09 Jun 2019 21:10:32 +0000 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BCBC7206BB; Sun, 9 Jun 2019 21:10:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560114629; bh=lvVVeecCiI6euXZs7+7PX8ChQOT7VlQhyz/VR+3FK5k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=yXim0t1zlSwmiV2eBumsQkrIYpbnDX5mYt/SgCDQxTcXOVHSPObkQQSyrlvXnjExG urv2S9tdXXyu4RWLWkAg01p6F3QuCTWI+H8mZjCAy906pZAt2GL+BONo3UfJmYkM6x 9W9RYtchmg9C5LPxz6L3wh7KEGjcUqLC+GaV2Oys= Date: Sun, 9 Jun 2019 23:10:26 +0200 From: Greg KH To: Dragan Cvetic Subject: Re: [PATCH V5 02/11] misc: xilinx-sdfec: add core driver Message-ID: <20190609211026.GA9859@kroah.com> References: <1560038656-380620-1-git-send-email-dragan.cvetic@xilinx.com> <1560038656-380620-3-git-send-email-dragan.cvetic@xilinx.com> <20190609112235.GA16574@kroah.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190609_141031_341811_4A9E557B X-CRM114-Status: GOOD ( 27.74 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "mark.rutland@arm.com" , "devicetree@vger.kernel.org" , "arnd@arndb.de" , "linux-kernel@vger.kernel.org" , "robh+dt@kernel.org" , Michal Simek , Derek Kiernan , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sun, Jun 09, 2019 at 06:48:31PM +0000, Dragan Cvetic wrote: > > > > -----Original Message----- > > From: Greg KH [mailto:gregkh@linuxfoundation.org] > > Sent: Sunday 9 June 2019 12:23 > > To: Dragan Cvetic > > Cc: arnd@arndb.de; Michal Simek ; linux-arm-kernel@lists.infradead.org; robh+dt@kernel.org; > > mark.rutland@arm.com; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; Derek Kiernan > > Subject: Re: [PATCH V5 02/11] misc: xilinx-sdfec: add core driver > > > > On Sun, Jun 09, 2019 at 01:04:07AM +0100, Dragan Cvetic wrote: > > > Implement a platform driver that matches with xlnx, > > > sd-fec-1.1 device tree node and registers as a character > > > device, including: > > > - SD-FEC driver binds to sdfec DT node. > > > - creates and initialise an initial driver dev structure. > > > - add the driver in Linux build and Kconfig. > > > > > > Tested-by: Dragan Cvetic > > > Signed-off-by: Derek Kiernan > > > Signed-off-by: Dragan Cvetic > > > --- > > > drivers/misc/Kconfig | 12 +++++ > > > drivers/misc/Makefile | 1 + > > > drivers/misc/xilinx_sdfec.c | 118 ++++++++++++++++++++++++++++++++++++++++++++ > > > 3 files changed, 131 insertions(+) > > > create mode 100644 drivers/misc/xilinx_sdfec.c > > > > > > diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig > > > index 6b0417b..319a6bf 100644 > > > --- a/drivers/misc/Kconfig > > > +++ b/drivers/misc/Kconfig > > > @@ -471,6 +471,18 @@ config PCI_ENDPOINT_TEST > > > Enable this configuration option to enable the host side test driver > > > for PCI Endpoint. > > > > > > +config XILINX_SDFEC > > > + tristate "Xilinx SDFEC 16" > > > + help > > > + This option enables support for the Xilinx SDFEC (Soft Decision > > > + Forward Error Correction) driver. This enables a char driver > > > + for the SDFEC. > > > + > > > + You may select this driver if your design instantiates the > > > + SDFEC(16nm) hardened block. To compile this as a module choose M. > > > + > > > + If unsure, say N. > > > + > > > config MISC_RTSX > > > tristate > > > default MISC_RTSX_PCI || MISC_RTSX_USB > > > diff --git a/drivers/misc/Makefile b/drivers/misc/Makefile > > > index b9affcd..0cb3546 100644 > > > --- a/drivers/misc/Makefile > > > +++ b/drivers/misc/Makefile > > > @@ -59,3 +59,4 @@ obj-$(CONFIG_OCXL) += ocxl/ > > > obj-y += cardreader/ > > > obj-$(CONFIG_PVPANIC) += pvpanic.o > > > obj-$(CONFIG_HABANA_AI) += habanalabs/ > > > +obj-$(CONFIG_XILINX_SDFEC) += xilinx_sdfec.o > > > diff --git a/drivers/misc/xilinx_sdfec.c b/drivers/misc/xilinx_sdfec.c > > > new file mode 100644 > > > index 0000000..75cc980 > > > --- /dev/null > > > +++ b/drivers/misc/xilinx_sdfec.c > > > @@ -0,0 +1,118 @@ > > > +// SPDX-License-Identifier: GPL-2.0 > > > +/* > > > + * Xilinx SDFEC > > > + * > > > + * Copyright (C) 2019 Xilinx, Inc. > > > + * > > > + * Description: > > > + * This driver is developed for SDFEC16 (Soft Decision FEC 16nm) > > > + * IP. It exposes a char device which supports file operations > > > + * like open(), close() and ioctl(). > > > + */ > > > + > > > +#include > > > +#include > > > +#include > > > +#include > > > +#include > > > +#include > > > +#include > > > +#include > > > +#include > > > + > > > +static int xsdfec_ndevs; > > > > You should use an idr for this, not just a number you bump up and down. > > This will not work properly at all. > > > > Think about this situation: > > probe device 0 > > xsdfec_ndevs = 1 > > probe device 1 > > xsdfec_ndevs = 2 > > remove device 0 > > xsdfec_ndevs = 0 > > probe another device > > misc device fails due to duplicate name. > > > > My bad. > I can use idr, but couldn't be better optimized code if use simple mutex to protect the variable. mutex does not protect from this at all, it's a logic bug. Think about adding 5 devices and then removing the 2nd one. What is the number assigned to the new device that is added afterward? And you need a mutex for the idr anyway, if you are touching it in a non probe/release callback way (those are already serialized by the bus lock). thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel