Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753324AbbK3ISt (ORCPT ); Mon, 30 Nov 2015 03:18:49 -0500 Received: from mga14.intel.com ([192.55.52.115]:15208 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752886AbbK3ISs (ORCPT ); Mon, 30 Nov 2015 03:18:48 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,364,1444719600"; d="scan'208";a="696562442" Date: Mon, 30 Nov 2015 13:51:41 +0530 From: Vinod Koul To: Sinan Kaya Cc: dmaengine@vger.kernel.org, timur@codeaurora.org, cov@codeaurora.org, jcm@redhat.com, agross@codeaurora.org, arnd@arndb.de, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V7 2/3] dma: add Qualcomm Technologies HIDMA management driver Message-ID: <20151130082141.GB3901@localhost> References: <1448245707-27499-1-git-send-email-okaya@codeaurora.org> <1448245707-27499-3-git-send-email-okaya@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1448245707-27499-3-git-send-email-okaya@codeaurora.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2452 Lines: 76 On Sun, Nov 22, 2015 at 09:28:24PM -0500, Sinan Kaya wrote: > +++ b/Documentation/ABI/testing/sysfs-platform-hidma-mgmt > @@ -0,0 +1,97 @@ > +What: /sys/devices/platform/hidma-mgmt*/chan*/priority > + /sys/devices/platform/QCOM8060:*/chan*/priority > +Date: Nov 2015 > +KernelVersion: 4.4 > +Contact: "Sinan Kaya " > +Description: > + Contains either 0 or 1 and indicates if the DMA channel is a > + low priority (0) or high priority (1) channel. What is purpose of adding sysfs entries here ? > + > +#define QOS_N_OFFSET 0x300 > +#define CFG_OFFSET 0x400 > +#define MAX_BUS_REQ_LEN_OFFSET 0x41C > +#define MAX_XACTIONS_OFFSET 0x420 > +#define HW_VERSION_OFFSET 0x424 > +#define CHRESET_TIMEOUT_OFFSET 0x418 > + > +#define MAX_WR_XACTIONS_MASK GENMASK(4, 0) > +#define MAX_RD_XACTIONS_MASK GENMASK(4, 0) > +#define WEIGHT_MASK GENMASK(6, 0) > +#define MAX_BUS_REQ_LEN_MASK GENMASK(15, 0) > +#define CHRESET_TIMEOUUT_MASK GENMASK(19, 0) > + > +#define MAX_WR_XACTIONS_BIT_POS 16 > +#define MAX_BUS_WR_REQ_BIT_POS 16 > +#define WRR_BIT_POS 8 > +#define PRIORITY_BIT_POS 15 > + > +#define AUTOSUSPEND_TIMEOUT 2000 > +#define MAX_CHANNEL_WEIGHT 15 These names are quite generic and prone to collide with generic names, please prefix them with your driver name > +} > +EXPORT_SYMBOL_GPL(hidma_mgmt_setup); Why is this exported or rather who would be users of this? > +static int hidma_mgmt_probe(struct platform_device *pdev) > +{ > + struct hidma_mgmt_dev *mgmtdev; > + struct resource *res; > + void __iomem *virtaddr; > + int irq; > + int rc; > + u32 val; > + > + pm_runtime_set_autosuspend_delay(&pdev->dev, AUTOSUSPEND_TIMEOUT); > + pm_runtime_use_autosuspend(&pdev->dev); > + pm_runtime_set_active(&pdev->dev); > + pm_runtime_enable(&pdev->dev); at this time pm core will treat device as fully enabled and pm methods can be invoked, but you are not ready yet right. Typically these are done at the end of the probe unless you have a reason... > +static ssize_t show_values(struct device *dev, struct device_attribute *attr, > + char *buf) Please fix the coding style here and other places as well. Specifically please read Chapter 2 -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/