Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp552701ybl; Wed, 21 Aug 2019 01:44:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqyQxiQmrpzzH0wYxlo5DGVbIVOT90cvdtWrbljZAk/3og0kby6N8Jn3t2tyKAupp4opnqXk X-Received: by 2002:a17:902:a8:: with SMTP id a37mr16848673pla.316.1566377049235; Wed, 21 Aug 2019 01:44:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566377049; cv=none; d=google.com; s=arc-20160816; b=C/7/FR2GFGKpPg/ed6qDwWXSRuCtllEpHBEF5C+eAB9rjuzgLcjbfLZcheEOSm788o Ju+1nq0aO6hyQUGFGqNjWBbTVppRSfGpAVBJfBnczO8OfEsYTNtAu6cA1qNDEi0BQYUn /sWtihJ89KoNtQlnxm3C0F3RsQn4KmwEsJirC3tR9CLihOVn63nN/HpX46rloOj7Vs+V 3Z4ZpM6nUOKdLKwiyRBYow9RN+n3WkebSntwsgFIvbCKDjablqC0ANHlOLInDQZWCeiA zOPxgYPHgv9+lSYr1eAFuS2L2oIePH/Dpkj/9Wr0V9MPkJ6iVTCQIhOkwoaLYdelCP4a zI1A== 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=m5QZ0lchold4r9N5xqjp6rG0qkUnxEfLj3xQsQk/KLo=; b=tQ83T6V/dROTMGyeSPEDoABynbr/DLKb5S9Y4rqk3/KFAIrq1dofR5+ryrbXOYyTUc zZsMTKZBBv4rQWahUPnof0ncJE3/O2TW58LjFZ9DH+150ZY9V6mxH0gq4MdyEvAMKpDs 0GljPWd9pb2vGccAhSmwb7qiR+h1t4NCUpsMD4A5Xgbwehk8PTWDvOcCMC5NHAIKSeCQ j68kf+1uUmfg5ES+au9x7b1mt38r7CJwbaqJQ4b1MOB8MTHKtWPsEIaLyss8BADK99nM lE7kT6fOEhXDD2YnAAJ+b1WXtUg+G58ofSzuHGtXhqdQUNDRQY/ZdNUA1KA3WwFmPHCN JCOg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="P7/gmtEO"; 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 h26si13776180pgl.398.2019.08.21.01.43.53; Wed, 21 Aug 2019 01:44:09 -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="P7/gmtEO"; 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 S1726330AbfHUHtv (ORCPT + 99 others); Wed, 21 Aug 2019 03:49:51 -0400 Received: from mail.kernel.org ([198.145.29.99]:58362 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726028AbfHUHtv (ORCPT ); Wed, 21 Aug 2019 03:49:51 -0400 Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) (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 CADD7233FF; Wed, 21 Aug 2019 07:49:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566373790; bh=48hZbPJtzSxx3b/A53I4PAXECxqgXTQufB/rcB8xTZM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=P7/gmtEOu+07urJK1FBTX+Ba4qDgS5ToQMx4eze7JbceXNNUR4u4m49iHD74LH3cp ZheENFVTNDmU4heunGKuD/ax/z6UiPmx6Al6Q1gc9brqPjwPysWKUVE5GyeFPUNyvH dXNfVYg87CsT9axD9YizhBrmwa4WId7PNziUkEjU= Received: by mail-lj1-f170.google.com with SMTP id x3so1228163lji.5; Wed, 21 Aug 2019 00:49:49 -0700 (PDT) X-Gm-Message-State: APjAAAW3jPLlNI4HDPu2txBHd0BvA44pljrd4VYETRb4z2WeGoqa4dgh rJtoteaF8SkbsbjCCh+B7xl8vh4c7iIExez2pwI= X-Received: by 2002:a2e:9acf:: with SMTP id p15mr18348273ljj.13.1566373787954; Wed, 21 Aug 2019 00:49:47 -0700 (PDT) MIME-Version: 1.0 References: <20190813150827.31972-1-s.nawrocki@samsung.com> <20190813150827.31972-3-s.nawrocki@samsung.com> <1e428c8e-f4b5-0810-77f9-2c899c040fc7@kernel.org> In-Reply-To: <1e428c8e-f4b5-0810-77f9-2c899c040fc7@kernel.org> From: Krzysztof Kozlowski Date: Wed, 21 Aug 2019 09:49:36 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 2/9] soc: samsung: Convert exynos-chipid driver to use the regmap API To: Sylwester Nawrocki Cc: Jon Hunter , Sylwester Nawrocki , 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 , linux-tegra , Arnd Bergmann 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 Tue, 20 Aug 2019 at 23:38, Sylwester Nawrocki wrote: > > On 8/20/19 21:37, Krzysztof Kozlowski wrote: > >>> diff --git a/drivers/soc/samsung/exynos-chipid.c b/drivers/soc/samsung/exynos-chipid.c > > >>> @@ -51,29 +48,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("Failed to get CHIPID regmap\n"); > >>> + return PTR_ERR(regmap); > >>> } > >> Following this change, I am now seeing the above error on our Tegra > >> boards where this driver is enabled. This is triggering a kernel > >> warnings test we have to fail. Hence, I don't think that you can remove > >> the compatible node test here, unless you have a better way to determine > >> if this is a samsung device. > > > > Right, this is really wrong... I missed that it is not a probe but > > early init. And this init will be called on every board... Probably it > > should be converted to a regular driver. > > I'm also inclined to have it converted to a regular driver. We already > have "exynos-asv" driver matching on the chipid node (patch 3/9). > The ASV patches will not be merged soon anyway, all this needs some more > thought. Krzysztof, can we abandon the chipid patches for now? Your > pull request doesn't appear to be merged to arm-soc yet. Sorry about > that. Yes, let's abandon the pull request and rework the concept. Best regards, Krzysztof