Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp2931546imm; Fri, 19 Oct 2018 02:05:20 -0700 (PDT) X-Google-Smtp-Source: ACcGV604T7LqoKitgA3hJkrvUA3E9x057AesLGNsiEvcV0QKVMMBce+8yEpAn4hTau3i1a1ib3Qc X-Received: by 2002:a63:a80c:: with SMTP id o12-v6mr31975076pgf.271.1539939919944; Fri, 19 Oct 2018 02:05:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539939919; cv=none; d=google.com; s=arc-20160816; b=C/rekCsGZDCGSR0xWodra4ww2Beflo4MobLCXnChuP94RdNz2X2SwsRKg/+8TAs/G2 CJ0HXUORY33IxuhokqhwE0+TMqEktc+v+zdHBtgxn32txYJikRXsl+z0veqaeeqs29GR cNkAfA3J4b/0QT/qdbB13tmpBSyHCWZFmFE7GuF4qBSJJc8UEXLEPIiiE7zOCJuK7uUp aeaDB+lVm6Ljg1nQM3q651gKpBqSq5zLlRvQwbhgwtGfju5+c8xxy1ocwvZcVOlu1SsY GSMBGnvj0NwjHyz7rGaCKWFymFuz7Xp4ZKfQEjiwzsfom+sOwXMCKqKhlUkoAcEMrb/b Zw2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:to:from:subject:message-id; bh=Uj0eK+oFIXGG61UzyqAbpcCwD4NGLScPD3Do+xxO6/U=; b=asEWPYkcAOBLx0jctExuQjufsEQQ1UNoYCltDZ794pVkZ09egQPpvwDxTCOFm0falC zDIEUAtj2IAexe+o87BaM1b0aZRXtn8+XmHh7mxB4AzbMeEZfPzFBtoDxQyFv8pY52Qg 9JL5WJsEvCX6UKxsSPqMjcl9ITqJKkfLsNiku6xPYMFybppa+aQXWKm2SJ9Osb0EIBGX X1+fHW5Uh7GQyng7N/fTh8Jh4bQtOyGdCHbA7siqqIl1JXRy3IAaudtGZpKLH58WvVer Pey2VPR/xOP0sHWm9n+B4pf/Sf+Sk0T5KW0cch1Fd7wsUprJan4JKrIT21SwLdLYIzpJ BRtw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m10-v6si23170709pgb.101.2018.10.19.02.05.03; Fri, 19 Oct 2018 02:05:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727220AbeJSRIf (ORCPT + 99 others); Fri, 19 Oct 2018 13:08:35 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:58179 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726399AbeJSRIf (ORCPT ); Fri, 19 Oct 2018 13:08:35 -0400 Received: from lupine.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:1a17] helo=lupine) by metis.ext.pengutronix.de with esmtp (Exim 4.89) (envelope-from ) id 1gDQgc-0004Tc-6i; Fri, 19 Oct 2018 11:03:14 +0200 Message-ID: <1539939793.3395.2.camel@pengutronix.de> Subject: Re: [PATCH 3/3] reset: reset-zynqmp: Adding support for Xilinx zynqmp reset controller. From: Philipp Zabel To: Nava kishore Manne , robh+dt@kernel.org, mark.rutland@arm.com, michal.simek@xilinx.com, rajanv@xilinx.com, jollys@xilinx.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, chinnikishore369@gmail.com Date: Fri, 19 Oct 2018 11:03:13 +0200 In-Reply-To: <20181020084107.28251-4-nava.manne@xilinx.com> References: <20181020084107.28251-1-nava.manne@xilinx.com> <20181020084107.28251-4-nava.manne@xilinx.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:1a17 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Nava, On Sat, 2018-10-20 at 14:11 +0530, Nava kishore Manne wrote: > Add a reset controller driver for Xilinx Zynq UltraScale+ MPSoC. > The zynqmp reset-controller has the ability to reset lines > connected to different blocks and peripheral in the Soc. > > Signed-off-by: Nava kishore Manne > --- > Changes for v1: > -None. I had comments on RFC v3 that are not addressed yet, see below. > --- /dev/null > +++ b/drivers/reset/reset-zynqmp.c > @@ -0,0 +1,117 @@ > +// SPDX-License-Identifier: GPL-2.0+ > +/* > + * Copyright (C) 2018 Xilinx, Inc. > + * > + */ > + > +#include Unnecessary. [...] > +static int zynqmp_reset_status(struct reset_controller_dev *rcdev, > + unsigned long id) > +{ > + struct zynqmp_reset_data *priv = to_zynqmp_reset_data(rcdev); > + int val, err; > + > + err = priv->eemi_ops->reset_get_status(ZYNQMP_RESET_ID + id, &val); > + if (!err) > + return -EINVAL; Should return error code, and only if there is an error: if (err) return err; > + return val; > +} > + > +static int zynqmp_reset_reset(struct reset_controller_dev *rcdev, > + unsigned long id) > +{ > + struct zynqmp_reset_data *priv = to_zynqmp_reset_data(rcdev); > + > + return priv->eemi_ops->reset_assert(ZYNQMP_RESET_ID + id, > + PM_RESET_ACTION_PULSE); > +} > + > +static struct reset_control_ops zynqmp_reset_ops = { Should be const: static const struct reset_control_ops zynqmp_reset_ops = { > + .reset = zynqmp_reset_reset, > + .assert = zynqmp_reset_assert, > + .deassert = zynqmp_reset_deassert, > + .status = zynqmp_reset_status, > +}; > + > +static int zynqmp_reset_probe(struct platform_device *pdev) > +{ > + struct zynqmp_reset_data *priv; > + > + priv = devm_kzalloc(&pdev->dev, > + sizeof(*priv), GFP_KERNEL); Fits on one line: priv = devm_kzalloc(&pdev->dev, sizeof(*priv), GFP_KERNEL); regards Philipp