Received: by 10.213.65.68 with SMTP id h4csp1579511imn; Mon, 19 Mar 2018 07:57:56 -0700 (PDT) X-Google-Smtp-Source: AG47ELu6QodmglvooNy1KnPbZ3b1cdSw0jxqixxG90vF4busLbGW4h3Aru4UzKPb2aeu06Q4BROm X-Received: by 10.101.90.10 with SMTP id y10mr9346006pgs.34.1521471476857; Mon, 19 Mar 2018 07:57:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521471476; cv=none; d=google.com; s=arc-20160816; b=n8noJWrgw8CkVs7QgOO74xJjkpd5vRkmHEY4x0abgd43VHeThC7rlK6yMsqNigHRDX PfxEQRnBI92bInOzwq4DTaLrrTw1jynYq17REGodvzQFW8xUXoIHFMc848Y7z2oMm1XY HEbBh3lgzOfdyvBzi3ADmHTSE2jQYeW6G/JJd+7YUP6WO2eQpw92Z49+iS4AKbQdIwdf USLAzru67eZB7lRhINGwAx/vCgJ7zo6JKHcf9Ofq8XyV5Ba4wsYX5rav5NyE1+yb5kiF 2thgQupVzN7prcQVmx5BsGLBCXZshk38/2hLT2HuBhhLi3JYrDdmd0RfLQsI1TA+e1mc PftQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dmarc-filter:dkim-signature :dkim-signature:arc-authentication-results; bh=GkhhsaQ8WCDtskPVgb62aEG607LA7PZup/UPvFd3cwM=; b=PAE22fuMk2F7mL2X4gxHsEe8zTlliMjMBHg8xtTylsuyI3DounSD5x6FL+mE3nEMFz HiGosDhBdTux7IQ5BxjYqUasm066jlGpyEJT7Kp8UeWeZF7gMHqimxCk8wU5Zb1pGTW2 ogp1XLEPIoZ+jNsnOdZiSeAHYdVbzAYovx7h5h/WEbA20kQXZC04/N3oskzUKP0UQVYO EnbjCip1Ddgl8ruNVgSPGaDWKF4wOym8pCbKippKvg452gGx/5F6HtcyYoUVkXyWr3hQ yAUr2EOlEw0dlLVgU75ZTjuvyldXI1bo1SMAgh8IXoJYskmQzB79yx5L98hiCJq4Vw50 5KYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=eniFINQo; dkim=pass header.i=@codeaurora.org header.s=default header.b=eniFINQo; 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 k64si110642pfj.262.2018.03.19.07.57.41; Mon, 19 Mar 2018 07:57:56 -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; dkim=pass header.i=@codeaurora.org header.s=default header.b=eniFINQo; dkim=pass header.i=@codeaurora.org header.s=default header.b=eniFINQo; 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 S1755553AbeCSOzd (ORCPT + 99 others); Mon, 19 Mar 2018 10:55:33 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:52388 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755270AbeCSOz3 (ORCPT ); Mon, 19 Mar 2018 10:55:29 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 8DF3F607A2; Mon, 19 Mar 2018 14:55:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1521471328; bh=kXUveIpTNcenDk8TlwKUFTzcBVftKacH5q1JJrebk84=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=eniFINQoukqePhg2+UYJK9M1wm+ZfAEzrYrI3j4ksTjlyDKpXb0Xf2C6DkPvkOxLx 4BZth3p5swaxhKTdHIaZpRybIkxrMZAnqSJsFBPt7F8KNWu1xdnPxDdQ/c83AGEraN aPpeRTPJB2fM7IZOIc1pzugmfIZ5GycM1kdBaDeU= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from jcrouse-lnx.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jcrouse@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 65FAF6055D; Mon, 19 Mar 2018 14:55:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1521471328; bh=kXUveIpTNcenDk8TlwKUFTzcBVftKacH5q1JJrebk84=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=eniFINQoukqePhg2+UYJK9M1wm+ZfAEzrYrI3j4ksTjlyDKpXb0Xf2C6DkPvkOxLx 4BZth3p5swaxhKTdHIaZpRybIkxrMZAnqSJsFBPt7F8KNWu1xdnPxDdQ/c83AGEraN aPpeRTPJB2fM7IZOIc1pzugmfIZ5GycM1kdBaDeU= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 65FAF6055D Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=jcrouse@codeaurora.org Date: Mon, 19 Mar 2018 08:55:25 -0600 From: Jordan Crouse To: Channagoud Kadabi Cc: linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-arm@lists.infradead.org, linux-kernel@vger.kernel.org, tsoni@codeaurora.org, sboyd@codeaurora.org, kyan@codeaurora.org Subject: Re: [PATCH 2/2] drivers: soc: Add LLCC driver Message-ID: <20180319145525.GD28808@jcrouse-lnx.qualcomm.com> Mail-Followup-To: Channagoud Kadabi , linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-arm@lists.infradead.org, linux-kernel@vger.kernel.org, tsoni@codeaurora.org, sboyd@codeaurora.org, kyan@codeaurora.org References: <1516924513-20183-1-git-send-email-ckadabi@codeaurora.org> <1516924513-20183-3-git-send-email-ckadabi@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1516924513-20183-3-git-send-email-ckadabi@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 25, 2018 at 03:55:13PM -0800, Channagoud Kadabi wrote: > LLCC (Last Level Cache Controller) provides additional cache memory > in the system. LLCC is partitioned into muliple slices and each > slice gets its own priority, size, ID and other config parameters. > LLCC driver programs these parameters for each slice. Clients that > are assigned to use LLCC need to get information such size & ID of the > slice for their usecase and activate or deactivate the slice as needed. > LLCC driver provides API interfaces for the clients to perform these > operations. > +/** > + * llcc_slice_deactivate - Deactivate the llcc slice > + * @desc: Pointer to llcc slice descriptor > + * > + * A value zero will be returned on success and a negative errno will > + * be returned in error cases > + */ > +int llcc_slice_deactivate(struct llcc_slice_desc *desc) > +{ > + u32 act_ctrl_val; > + int rc = -EINVAL; > + struct llcc_drv_data *drv; > + > + if (desc == NULL) { > + pr_err("Input descriptor supplied is invalid\n"); Sorry that this is out of the blue, but I was reviewing a client driver that uses this API. This should not print an error - we should be allowed to safely pass a null pointer from an aborted sequence in the driver without the conditional checks and it shouldn't generate a bit of log spam as it goes about it's business. Jordan -- The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project