Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5961805ybi; Wed, 12 Jun 2019 11:27:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqw/M2Yb0wXboPSX4XHULv12qwNlJgetbx3cNiXx/gy9GI5s6Wjg3AiqM7y3nXiv+9YLVVnf X-Received: by 2002:a62:e417:: with SMTP id r23mr55266982pfh.160.1560364025831; Wed, 12 Jun 2019 11:27:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560364025; cv=none; d=google.com; s=arc-20160816; b=zvdlFsGLuKzxdRJZqfT/sSIJ4JSQjFyxGcOK++Z3EwPGf+vh15EXhCaWTy2cYC/uAV X5COjfs85iGHE0rGbAE4ACGQJH96G/PvQuupAAP0Lb0R7tjhZgn3R74fr0l5tVZKQQbR 34x63f1XTJVTTDRYFG02qXNVDNQa97JD94D5C1toGOP534mNftInSHDpYhGD5Svx+v+B qAznbmGjhEayY0BJNNwFF56ZtRfRGLI2uYGjFa7vMI9ZLPwr+jtCFrc4rm45Utq+fEyB cd65pxn/HSAay8gkgh22bRg0veukJnkEG3Zz0jkiNtX5ALGdemZbPFyH34Rz3KK9AP7W o/hQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=POCxOYqYc43+WlcENbRzLBJwsanmxqSi5J4OMLdCOB8=; b=EBncG+yejMfxPjoyzYSF/py5dMSyvEpNIiDfsLRVU8/4fHf+vCXvKmr0AhPeaqvyPx iPliHL+Ykr7rBIDjrGQukjeqI2Su6Y7kq7ZbLGR8na+tJVs4olTRiAu5BYyk3x5Td5AP yhN9IRR9wpiiztdxGkJOY+EVun9SYC9NXbcpke7aaNMlsGsZUOjVGtqSrereIj6SfDje eg583i0OyOqV/5l8SbHuF13oiNHNXNQJ0ZYJgJCFYuNI/R0nWcJtoEexGxMwrT5yMi9Q vcDTQPjy6vXr594cew/fabOaYZdfStMLOsTt6ol6RzAtUbs3UmOjMZ9zf10dtR88nLo6 b83A== ARC-Authentication-Results: i=1; mx.google.com; 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 d31si380344pla.84.2019.06.12.11.26.51; Wed, 12 Jun 2019 11:27:05 -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; 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 S1726599AbfFLSZQ (ORCPT + 99 others); Wed, 12 Jun 2019 14:25:16 -0400 Received: from mx2.suse.de ([195.135.220.15]:35240 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725497AbfFLSZQ (ORCPT ); Wed, 12 Jun 2019 14:25:16 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id B9B2CAFFA; Wed, 12 Jun 2019 18:25:14 +0000 (UTC) From: Nicolas Saenz Julienne To: stefan.wahren@i2se.com, linux-kernel@vger.kernel.org Cc: mbrugger@suse.de, viresh.kumar@linaro.org, rjw@rjwysocki.net, sboyd@kernel.org, eric@anholt.net, f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com, ptesarik@suse.com, linux-rpi-kernel@lists.infradead.org, ssuloev@orpaltech.com, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, mturquette@baylibre.com, linux-pm@vger.kernel.org, Nicolas Saenz Julienne Subject: [PATCH v4 0/7] cpufreq support for Raspberry Pi Date: Wed, 12 Jun 2019 20:24:52 +0200 Message-Id: <20190612182500.4097-1-nsaenzjulienne@suse.de> X-Mailer: git-send-email 2.21.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, this aims at adding cpufreq support to the Raspberry Pi family of boards. The series first factors out 'pllb' from clk-bcm2385 and creates a new clk driver that operates it over RPi's firmware interface[1]. We are forced to do so as the firmware 'owns' the pll and we're not allowed to change through the register interface directly as we might race with the over-temperature and under-voltage protections provided by the firmware. Next it creates a minimal cpufreq driver that populates the CPU's opp table, and registers cpufreq-dt. Which is needed as the firmware controls the max and min frequencies available. This was tested on a RPi3b+ and RPI2b, both using multi_v7_defconfig and arm64's defconfig. That's all, kind regards, Nicolas [1] https://github.com/raspberrypi/firmware/wiki/Mailbox-property-interface --- Changes since v3: - Fix sparse warnings in clk-raspberrypi.c - Minor cleanups Changes since v2: - Fixed configs to match Stefan's comments - Round OPP frequencies - Rebase onto linux-next - Minor cleanups & checkpatch.pl Changes since v1: - Enabled by default on the whole family of devices - Added/Fixed module support - clk device now registered by firmware driver - raspberrypi-cpufreq device now registered by clk driver - Reimplemented clk rounding unsing determine_rate() - Enabled in configs for arm and arm64 Changes since RFC: - Move firmware clk device into own driver Nicolas Saenz Julienne (7): clk: bcm2835: remove pllb clk: bcm283x: add driver interfacing with Raspberry Pi's firmware firmware: raspberrypi: register clk device cpufreq: add driver for Raspberry Pi clk: raspberrypi: register platform device for raspberrypi-cpufreq ARM: defconfig: enable cpufreq driver for RPi arm64: defconfig: enable cpufreq support for RPi3 arch/arm/configs/bcm2835_defconfig | 9 + arch/arm/configs/multi_v7_defconfig | 2 + arch/arm64/configs/defconfig | 2 + drivers/clk/bcm/Kconfig | 7 + drivers/clk/bcm/Makefile | 1 + drivers/clk/bcm/clk-bcm2835.c | 28 +-- drivers/clk/bcm/clk-raspberrypi.c | 315 ++++++++++++++++++++++++++ drivers/cpufreq/Kconfig.arm | 8 + drivers/cpufreq/Makefile | 1 + drivers/cpufreq/raspberrypi-cpufreq.c | 97 ++++++++ drivers/firmware/raspberrypi.c | 10 + 11 files changed, 456 insertions(+), 24 deletions(-) create mode 100644 drivers/clk/bcm/clk-raspberrypi.c create mode 100644 drivers/cpufreq/raspberrypi-cpufreq.c -- 2.21.0