Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp8834669ybi; Tue, 23 Jul 2019 16:20:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqw2jEODyi8ioJnkKIe7Fxexo5Zp2Ssp/5BzOFfe/mEtOHJ5cA7vrdcVQSFdCEP/9+Yd3gGS X-Received: by 2002:a63:db47:: with SMTP id x7mr78014463pgi.375.1563924006610; Tue, 23 Jul 2019 16:20:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563924006; cv=none; d=google.com; s=arc-20160816; b=NMmD03M+OQQGQwyZFAAwggK7OOQIYdl5+IRvfffgvFQYVk0Ux98IdMyq7Ya3Ne2PEJ 2dUoQgyWnvl3tN4+DE2gLPHw1dw/7PleZxYCZosTgWTscHVtaJUVfqrokhamUboMf17N 2xu0HzZ46DHDfYVE+3aP4BO3jy07/6TPiQX879BQ70o++KbOYTA2Mgh/QvTbfTOmXGhk 2IHiB0EfIzkIseYlavllDkpIxUnqaqIRjN5ZL4fzNOAOTdRnAgptZTs2G7e8oQ1pFMQO DLUzpM5sZn5oa8nqwAQhlBoc4qhB21ZRFYvITPfvuGks2goZgG6PqCpaamXH04ffng9l YmJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=/vYfYDqZnmIRZfjdxg/K5NmBJTjS6xVQEQh21XD+Gzc=; b=S8ncR4e7e+648fXYJ9VPJe7wZF2jdUxicRVX8SGKAcSOhqJKZcbB2ZrBEQHtrcH3ty IWmdPWanmLhXEskZh4a6fUQS6qsTM5QhyNQ8q1ulmVmo7jZIYHaL5wHIkNjQhnyudMoA zgSZlTp8UAgF9bRJ2SL1F+J0+RTKqXZR2n/9AqItTN95DYyOB6tIgSq8Y01uqMZNro1s R8BeyDuNY0irhf50rI9378JHEOdqG9xkrA/dPtfbWVbZBxsMWMKMcyPJGRkFwu55xTS/ k8qGlyN4YZTi71jc7TWDfh0gvQJU9UIpR/dgWaEZlUp4iVB+cGr7lOBv1uQLuolZ+sdG fMLw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=kJ666ehf; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id co12si11889765plb.197.2019.07.23.16.19.51; Tue, 23 Jul 2019 16:20:06 -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=@kernel.org header.s=default header.b=kJ666ehf; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390036AbfGWNB0 (ORCPT + 99 others); Tue, 23 Jul 2019 09:01:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:35384 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387961AbfGWNB0 (ORCPT ); Tue, 23 Jul 2019 09:01:26 -0400 Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8891921670; Tue, 23 Jul 2019 13:01:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563886884; bh=CbmDLMjMi+Nd5R6Pl1B66vsTFwAu0X8Od5ob6t3Otuw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=kJ666ehfoUBAoI2YSx+SVUOL2NzcWGe+pasJx61NM0E2XfSz5lGrmUerxSGuy6lXL YHaLk0zDxiYnhzlDZ4vDTkSbddvYgI1I/A6hwhecveTCjW7DbHEDWDsSNunSb/rgj7 2Fhuuj2LpNazuUXoan0XpsuOKxvCQ8EoLnBZDIso= Received: by mail-lf1-f42.google.com with SMTP id z15so25009600lfh.13; Tue, 23 Jul 2019 06:01:24 -0700 (PDT) X-Gm-Message-State: APjAAAW38tGBwuCn9IW8FRqUH3x2Kd93SZo9VfAhcYcEQNiN8kbnMqEt DODAAav8+5Mb0XUC0QAtv7wvbwp0LibAKfkTVcI= X-Received: by 2002:ac2:514b:: with SMTP id q11mr9488330lfd.33.1563886882779; Tue, 23 Jul 2019 06:01:22 -0700 (PDT) MIME-Version: 1.0 References: <20190718143044.25066-1-s.nawrocki@samsung.com> <20190718143044.25066-3-s.nawrocki@samsung.com> In-Reply-To: <20190718143044.25066-3-s.nawrocki@samsung.com> From: Krzysztof Kozlowski Date: Tue, 23 Jul 2019 15:01:11 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/9] soc: samsung: Convert exynos-chipid driver to use the regmap API To: Sylwester Nawrocki Cc: robh+dt@kernel.org, vireshk@kernel.org, devicetree@vger.kernel.org, kgene@kernel.org, pankaj.dubey@samsung.com, "linux-samsung-soc@vger.kernel.org" , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= , Marek Szyprowski Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 18 Jul 2019 at 16:31, Sylwester Nawrocki wrote: > > Convert the driver to use regmap API in order to allow other > drivers, like ASV, to access the CHIPID registers. > > This patch adds definition of selected CHIPID register offsets > and register bit fields for Exynos5422 SoC. > > Signed-off-by: Sylwester Nawrocki > --- > Changes since v1 (RFC): > - new patch > --- > drivers/soc/samsung/exynos-chipid.c | 33 ++++++---------- > include/linux/soc/samsung/exynos-chipid.h | 48 +++++++++++++++++++++++ > 2 files changed, 61 insertions(+), 20 deletions(-) > create mode 100644 include/linux/soc/samsung/exynos-chipid.h > > diff --git a/drivers/soc/samsung/exynos-chipid.c b/drivers/soc/samsung/exynos-chipid.c > index 78b123ee60c0..594b00488013 100644 > --- a/drivers/soc/samsung/exynos-chipid.c > +++ b/drivers/soc/samsung/exynos-chipid.c > @@ -9,18 +9,16 @@ > */ > > #include > +#include > #include > #include > #include > #include > +#include > #include > +#include > #include > > -#define EXYNOS_SUBREV_MASK (0xF << 4) > -#define EXYNOS_MAINREV_MASK (0xF << 0) > -#define EXYNOS_REV_MASK (EXYNOS_SUBREV_MASK | EXYNOS_MAINREV_MASK) > -#define EXYNOS_MASK 0xFFFFF000 > - > static const struct exynos_soc_id { > const char *name; > unsigned int id; > @@ -53,29 +51,24 @@ static const char * __init product_id_to_soc_id(unsigned int product_id) > int __init exynos_chipid_early_init(void) > { > struct soc_device_attribute *soc_dev_attr; > - void __iomem *exynos_chipid_base; > struct soc_device *soc_dev; > struct device_node *root; > - struct device_node *np; > + struct regmap *regmap; > u32 product_id; > u32 revision; > + int ret; > > - /* look up for chipid node */ > - np = of_find_compatible_node(NULL, NULL, "samsung,exynos4210-chipid"); > - if (!np) > - return -ENODEV; > - > - exynos_chipid_base = of_iomap(np, 0); > - of_node_put(np); > - > - if (!exynos_chipid_base) { > - pr_err("Failed to map SoC chipid\n"); > - return -ENXIO; > + regmap = syscon_regmap_lookup_by_compatible("samsung,exynos4210-chipid"); > + if (IS_ERR(regmap)) { > + pr_err("%s: failed to get regmap\n", __func__); Other places do not use __func__ prefix so make it consistent. Add it in patch #1? > + return PTR_ERR(regmap); > } > > - product_id = readl_relaxed(exynos_chipid_base); > + ret = regmap_read(regmap, EXYNOS_CHIPID_REG_PRO_ID, &product_id); > + if (ret < 0) > + return ret; > + > revision = product_id & EXYNOS_REV_MASK; > - iounmap(exynos_chipid_base); > > soc_dev_attr = kzalloc(sizeof(*soc_dev_attr), GFP_KERNEL); > if (!soc_dev_attr) > diff --git a/include/linux/soc/samsung/exynos-chipid.h b/include/linux/soc/samsung/exynos-chipid.h > new file mode 100644 > index 000000000000..25359d70d617 > --- /dev/null > +++ b/include/linux/soc/samsung/exynos-chipid.h > @@ -0,0 +1,48 @@ > +/* SPDX-License-Identifier: GPL-2.0 */ > +/* > + * Copyright (c) 2018 Samsung Electronics Co., Ltd. > + * http://www.samsung.com/ > + * > + * Exynos - CHIPID support > + */ > + > +#define EXYNOS_CHIPID_REG_PRO_ID 0x00 > + #define EXYNOS_SUBREV_MASK (0xf << 4) " #define" is unusual syntax. I think not used anywhere else. Stick to regular one. Best regards, Krzysztof