Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp701414pxf; Thu, 25 Mar 2021 12:00:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxTmKTqL7FMcIIwhGnsVpZVIeQ0rXBIXELzHHCR0Ecl9YVjNFDzzsyTXi6Xq7IguMHIaEQ7 X-Received: by 2002:a17:906:5a8f:: with SMTP id l15mr11178279ejq.462.1616698827282; Thu, 25 Mar 2021 12:00:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616698827; cv=none; d=google.com; s=arc-20160816; b=TbYdqTdbF9eyO1sh1yNGh8UvfQUzLdikvODG5F+iBDBVLX5jqnWiAGzFbaZpRzy1lt yeECup5e8yiaRsGjAqawh4pqtqaTG6DftmUNuDmms4QaJtjL9LINNZzR8ugo06NWQcQ6 TGUpYTo7AP8d9SYfDenYFcmCxgxypVh4irunnzSI3j4LNsjIUNVm2a8TC4TeTBBgXGAF Q5xEiHW8RFRwdo5kHHConhy0uo2haQyQ/oN22g9zM1g2pgRGYHzqjNQyA/+eHVCLD4Mx sqvQx4jMqSjT5ev2uiqH0bcQ/Y+MjlG36NRgeazL/NncFF+3VAfqzc6CkLbL6XCMGtIy pLbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=FDESrIjFGFNqWBM9VK6nrsYhX4gnwWsF/as+YDweAYc=; b=rsCbwDuI31rkSNrltOzJ+KYD2ComGGlL3pQsvDWON2XxA8o266s8QDNeRVNc+eo+UL 64rEylL0JcdB4L8FUBVBMwh3GNeYG8XoeG/zRJlRnfCV3IvbxfJ73l++ewHGvDOJlV+Q IUGDRnlM6O7Ei6nNWqGg0Ek5Ue0CLAw2seqhha57Nd2wtCCz+isw4LpBIwIGDxIqjTi/ byoFrmMRgUocMnyFdFukxa6Yq4aAd2JMxTrVLJA/Zwz8cFP2K58BFD7x1qNWWJE+JtNn a3ibTNJjJOj17NWg9CiGjpD3GdDzHzeBnsct0gDkfJiRHpA42wL/pFg4dvuUMcdQIoST h2Ag== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=rIn+wgGd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id ay20si4887209ejb.414.2021.03.25.12.00.04; Thu, 25 Mar 2021 12:00:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=rIn+wgGd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S230195AbhCYS6Y (ORCPT + 99 others); Thu, 25 Mar 2021 14:58:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:38340 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230106AbhCYS6G (ORCPT ); Thu, 25 Mar 2021 14:58:06 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4DFC3617ED; Thu, 25 Mar 2021 18:58:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1616698686; bh=V8i1nTdRt1Uz7kSkKL6+utuHB72YqtcP7TDHOdswO9I=; h=From:To:Cc:Subject:Date:From; b=rIn+wgGdxVRjC8PgFaG04AFg8ZzorLICy8zOne7EqLGTHmrmW7vwlG4OO5az/Cthf uGy0dj6rvA0G2XX7tDgETsVbC3pAdBJHyozdf+FotjkTzaYXtcrclLI3hW+2tLI4x5 ZCAx83ItgJ3wbidgmOQL6M6glxjUpxOyHqHMbGqDLoD2dWa7m85rfNmufV7iCmkw6S C6scREPJk8E1uIaFKSjFXcfjpIXZ96SvmpYC6iKMdk2ExYu/iDriN45mEDUnvjGuD7 Qnnb0oqj5rTSDd7Yowd1sY5rRZ/Cnjyq8qff3z42j0L5NkAQ3uB3Kvr8gaI2gTc1Xm zW8mHDwDD3O8A== From: Nicolas Saenz Julienne To: Stephen Boyd , Maxime Ripard , Nicolas Saenz Julienne Cc: linux-rpi-kernel@lists.infradead.org, geert@linux-m68k.org, Nicolas Saenz Julienne , Marek Szyprowski , Michael Turquette , linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH] clk: bcm: rpi: Don't register as OF provider if !dev->np Date: Thu, 25 Mar 2021 19:57:48 +0100 Message-Id: <20210325185749.27984-1-nsaenz@kernel.org> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There are two ways clk-raspberrypi might be registered: through device-tree or through an explicit platform device registration. The latter happens after firmware/raspberrypi's probe, and it's limited to RPi3s, which solely use the ARM clock to scale CPU's frequency. That clock is matched with cpu0's device thanks to the ARM clock being registered as a clkdev. In that scenario, don't register the device as an OF clock provider, as it makes no sense and will cause trouble. Fixes: d4b4f1b6b97e ("clk: bcm: rpi: Add DT provider for the clocks") Reported-by: Marek Szyprowski Signed-off-by: Nicolas Saenz Julienne --- drivers/clk/bcm/clk-raspberrypi.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/drivers/clk/bcm/clk-raspberrypi.c b/drivers/clk/bcm/clk-raspberrypi.c index f89b9cfc4309..27e85687326f 100644 --- a/drivers/clk/bcm/clk-raspberrypi.c +++ b/drivers/clk/bcm/clk-raspberrypi.c @@ -337,10 +337,12 @@ static int raspberrypi_clk_probe(struct platform_device *pdev) if (ret) return ret; - ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_onecell_get, - clk_data); - if (ret) - return ret; + if (dev->of_node) { + ret = devm_of_clk_add_hw_provider(dev, of_clk_hw_onecell_get, + clk_data); + if (ret) + return ret; + } rpi->cpufreq = platform_device_register_data(dev, "raspberrypi-cpufreq", -1, NULL, 0); -- 2.30.2