From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0BC19C48BD6 for ; Tue, 25 Jun 2019 23:02:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D2A09208E3 for ; Tue, 25 Jun 2019 23:02:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1561503742; bh=82RyR5pFqn05vyyNq4lzd/5m52MIeTMNFiRkCRUTQV0=; h=In-Reply-To:References:To:From:Subject:Cc:Date:List-ID:From; b=B9BPOghse6Y8n3lihBTEyhcyXHSHlky9AYaO/k09I4T532ifMO78xR2+QXSzmsln+ Yd4vHeVzPatjOq7R4h8jRDCWSIz0OC3j96ZQxf0wZuZ2wXfrjbUtuCjOj2xTU0aYTN hGNpprPBeU+6xuzmFmiuWu0+uMWk19CCCseiNRwY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726037AbfFYXCW (ORCPT ); Tue, 25 Jun 2019 19:02:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:51054 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725782AbfFYXCW (ORCPT ); Tue, 25 Jun 2019 19:02:22 -0400 Received: from kernel.org (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A1C772084B; Tue, 25 Jun 2019 23:02:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1561503741; bh=82RyR5pFqn05vyyNq4lzd/5m52MIeTMNFiRkCRUTQV0=; h=In-Reply-To:References:To:From:Subject:Cc:Date:From; b=VxhOM3T0rDZQLYc6U+By4eyc5T1Fg6CRnnOjooSqYTLKhmT0WzIfRkbcCbpHuNkUd SfdZrjYkzhyLLpm9MxCLhuxO6J1ugyIMAFleGIH7ckoKy9+stTLZIYRJk83AxLdGaZ xithUTuimVB8qjTsllcRV1+jXFeDlIjceJxL68DU= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <20190612182500.4097-1-nsaenzjulienne@suse.de> <6a9e1450-80ad-a13c-59d2-d0b39f25f67e@gmail.com> <7acfd967-0a82-5429-4eed-8b802e6620f5@i2se.com> To: Mike Turquette , Stefan Wahren From: Stephen Boyd Subject: Re: [PATCH v4 0/7] cpufreq support for Raspberry Pi Cc: Florian Fainelli , Nicolas Saenz Julienne , linux-kernel@vger.kernel.org, mbrugger@suse.de, viresh.kumar@linaro.org, rjw@rjwysocki.net, eric@anholt.net, 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, linux-pm@vger.kernel.org User-Agent: alot/0.8.1 Date: Tue, 25 Jun 2019 16:02:20 -0700 Message-Id: <20190625230221.A1C772084B@mail.kernel.org> Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Quoting Stefan Wahren (2019-06-22 02:54:47) > Hi Stephen, > hi Mike, >=20 > Am 13.06.19 um 06:31 schrieb Stefan Wahren: > > Hi Florian, > > hi Stephen, > > > > Am 13.06.19 um 05:31 schrieb Florian Fainelli: > >> On 6/12/2019 11:24 AM, Nicolas Saenz Julienne wrote: > >>> 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 firmwa= re. > >>> > >>> 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. > >> How do we go about merging this? Stefan, will you pick up patch 3, 6 a= nd > >> 7 and submit them for 5.3/5.4? Viresh has already picked up patch 4. > > is it possible to let patches 1,2, 3 and 5 go via clk-tree? > > > > I would take care of 6 and 7. > > > > Stefan > are you fine with the series, since Viresh already picked up patch 4? >=20 > are you okay with my suggestion above? >=20 Oh I missed this. I can apply the clk patches most likely assuming it doesn't break anything bisection-wise. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 60FE7C48BD5 for ; Tue, 25 Jun 2019 23:02:35 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 33DD62084B for ; Tue, 25 Jun 2019 23:02:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="GJaMaMcl"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="VxhOM3T0" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 33DD62084B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Message-Id:Date:Subject:From:To: References:In-Reply-To:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=jYeOTqdqGgiB3mqn4sasZqm7QkBr10gIRAkwZXzg0Cg=; b=GJaMaMcliwJclo CFtKK+YMUkmkg4UxJFjwmrLwLCv2p3/bVVVKnZvhmmrflybdSZJhNdM2wH2gBkDOZbx52NO9v27Xd q77Y5K6y3UIh5SBgUS+EXdv8nthVC6csb+1AF4tq3nUMSNxK+BrHFp2LETynNejem7HPfJs0kG9wd W/Dv5zfJ1Z1bLotxKEMlnqW7EEYNLi3i4HT76h2nAqENNl8yEsZ0tNcY2e4M+O+bFlfDrJs8GtGdN AUoMycNQZOtXQ83VVzJDjoHS6CIGTNE4nXEoKpriEGb5mfauqZ78r4nG5UJG2P6UeSx7loBOBiKOr O6KaT375jshpLqlEM9Tw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hfuSJ-0004ch-Hs; Tue, 25 Jun 2019 23:02:27 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hfuSE-0004b0-2f; Tue, 25 Jun 2019 23:02:25 +0000 Received: from kernel.org (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A1C772084B; Tue, 25 Jun 2019 23:02:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1561503741; bh=82RyR5pFqn05vyyNq4lzd/5m52MIeTMNFiRkCRUTQV0=; h=In-Reply-To:References:To:From:Subject:Cc:Date:From; b=VxhOM3T0rDZQLYc6U+By4eyc5T1Fg6CRnnOjooSqYTLKhmT0WzIfRkbcCbpHuNkUd SfdZrjYkzhyLLpm9MxCLhuxO6J1ugyIMAFleGIH7ckoKy9+stTLZIYRJk83AxLdGaZ xithUTuimVB8qjTsllcRV1+jXFeDlIjceJxL68DU= MIME-Version: 1.0 In-Reply-To: References: <20190612182500.4097-1-nsaenzjulienne@suse.de> <6a9e1450-80ad-a13c-59d2-d0b39f25f67e@gmail.com> <7acfd967-0a82-5429-4eed-8b802e6620f5@i2se.com> To: Mike Turquette , Stefan Wahren From: Stephen Boyd Subject: Re: [PATCH v4 0/7] cpufreq support for Raspberry Pi User-Agent: alot/0.8.1 Date: Tue, 25 Jun 2019 16:02:20 -0700 Message-Id: <20190625230221.A1C772084B@mail.kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190625_160222_233093_7D7F424C X-CRM114-Status: GOOD ( 14.08 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arm-kernel@lists.infradead.org, Florian Fainelli , ptesarik@suse.com, viresh.kumar@linaro.org, linux-pm@vger.kernel.org, rjw@rjwysocki.net, linux-kernel@vger.kernel.org, eric@anholt.net, bcm-kernel-feedback-list@broadcom.com, mbrugger@suse.de, ssuloev@orpaltech.com, linux-clk@vger.kernel.org, Nicolas Saenz Julienne , linux-rpi-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Quoting Stefan Wahren (2019-06-22 02:54:47) > Hi Stephen, > hi Mike, > > Am 13.06.19 um 06:31 schrieb Stefan Wahren: > > Hi Florian, > > hi Stephen, > > > > Am 13.06.19 um 05:31 schrieb Florian Fainelli: > >> On 6/12/2019 11:24 AM, Nicolas Saenz Julienne wrote: > >>> 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. > >> How do we go about merging this? Stefan, will you pick up patch 3, 6 and > >> 7 and submit them for 5.3/5.4? Viresh has already picked up patch 4. > > is it possible to let patches 1,2, 3 and 5 go via clk-tree? > > > > I would take care of 6 and 7. > > > > Stefan > are you fine with the series, since Viresh already picked up patch 4? > > are you okay with my suggestion above? > Oh I missed this. I can apply the clk patches most likely assuming it doesn't break anything bisection-wise. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel