Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp120535imj; Wed, 13 Feb 2019 05:44:38 -0800 (PST) X-Google-Smtp-Source: AHgI3IY4XfyBaFe+xUGKgE9Y4BSzJoX9lQwL1o+8jLZdnFHLGoo1Q/b0eU/salEBe49HsB0tWLdb X-Received: by 2002:a17:902:ab8f:: with SMTP id f15mr633960plr.218.1550065478105; Wed, 13 Feb 2019 05:44:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550065478; cv=none; d=google.com; s=arc-20160816; b=If+MZCJSotFGlt5OiA1mOkifIaKHczk026JK/S0DMhAz1A7ZnKv1Q9vip5aFmmxE56 1ynUGM97d/vGttWxrcMysEIHvmJY0c2meBO+xFtJeF6/3vUrq4sTR0YbVEiaRAkbjZms Ao7IR7tBAdp/7X++1Y3va5RK01lfmbubGmqGtlZ8vTYW4CYPJldju+Fv4cvQp+3UPvIT +Sr7iLwFtiL3MxDpS3/Bz90/p1p6JuGtgGOxR7ox87RAB+1uMSZAt1azZL1HS0u7sEcP Kiw3I2/Kyowk3tHxSpSu5PFhnaBGUecYvqGKk0RrBqRcL3VGjtaCS9Deod2zdKJjIh4f p7TQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=7/wA9bKDbtMGKDL+u8LUnnfnebexOgDkULd9V0FL2tE=; b=Q7Ly/GWukWIbUwfeNqhTao0IyoKVytel52MyCCVihweGJFxUCWWgUVthz+Q+Iilnu1 +E+ot2lJu/MRD+O3xG3vjCoTIk1ZRBMJJteObDdVf7G4gVuZM8cc9hTC4tNfhFNxuuBX AlpZKncBP3Hv2D4/104st/GWjJVFxUjLLtkxe7WVLtXbKliVVX+9M5n8Td5HV8mM1hQi puZGrnjOnPtH2Ggg7D02btpsaTf7bNR5vxOKFKRnJK6fzbsphekYSWQtq5arsPiawO13 9XnEUgrENHH4FuzFV6Q1duldmwhQ+HJ2ny9ZSgnQligI+9DqzsiJHI5CaWzNGI6P6pqn LJQQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=nr1pBAeb; 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=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r2si8557080pgm.73.2019.02.13.05.44.22; Wed, 13 Feb 2019 05:44:38 -0800 (PST) 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=@linaro.org header.s=google header.b=nr1pBAeb; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730594AbfBMKPG (ORCPT + 99 others); Wed, 13 Feb 2019 05:15:06 -0500 Received: from mail-pl1-f195.google.com ([209.85.214.195]:45215 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726317AbfBMKPF (ORCPT ); Wed, 13 Feb 2019 05:15:05 -0500 Received: by mail-pl1-f195.google.com with SMTP id r14so930154pls.12 for ; Wed, 13 Feb 2019 02:15:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=7/wA9bKDbtMGKDL+u8LUnnfnebexOgDkULd9V0FL2tE=; b=nr1pBAebs7PLUPoIJO5ok0jnU3a5IsvOFYglsg4W/0KYVH+Vo9r2WOktmoKOys5AAV /u5UClC9n8rtV4O/QVQC0ysNeeHXe8oBbsjWWLeVQ722phXkRCJ6Dv4eDNJxvJe4ETUh 1fdtLGLdOMdhNoUlZ0HkBvCWVYg88ANOCOiJGdqxuPYbL43Q5PsTdwqH067hTrcs/DzJ PifGoJWMo9mPxMKPTwRkCBeAkkYUH9u7yPJ1aEs+ML6++uCGMRN5ZOJ5NgP7mPPKpN+C iX2AfXhdP5zPIT5AiiIsjDZabOXW+2NZfLLKRpKgewzCNgum/cB4YasqOLsRWQYPw0Zp mo9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=7/wA9bKDbtMGKDL+u8LUnnfnebexOgDkULd9V0FL2tE=; b=itYsrCwmjJTpokIJwNplmeXmEl03iJLGON8YH51otusgpRxzzUfmNVVOJfi/7GWs0E 4qfyh5RCwgBBRPa1wH1DYIk/tMZxDMIj3H3sF4Jg8tVHr6h36qjWgNVT12Z4Qtpn2W0G fKzEzSiSk0hwyb7gfUpSv9m/ecp9LbQciuS1rsm6Tf2Ws063A8N8SkjuQQxW4099Fk+u xmYNF5yx7iAoKpqSXkN3f9pK63QtGgVqQUj0UWO6Ta9IYMaiFFJn6uzsNv35/Dr6xLFu b3Zt/15AqORupaMKzpYrp3f67SMDG/+wR/1lgur7zTZJH/PGo+hyA3Rpvqp56B/S5kqT p4DQ== X-Gm-Message-State: AHQUAuavIleWgrfM9o7Nf6BMX+Gw30kXH6rnjqjGIS12kh4skmYPvA9f c5IIF7zEHvvE01HjzFPWhI5bfg== X-Received: by 2002:a17:902:f096:: with SMTP id go22mr2650457plb.23.1550052904800; Wed, 13 Feb 2019 02:15:04 -0800 (PST) Received: from localhost ([122.172.102.63]) by smtp.gmail.com with ESMTPSA id l87sm30819083pfj.35.2019.02.13.02.15.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 02:15:04 -0800 (PST) Date: Wed, 13 Feb 2019 15:45:02 +0530 From: Viresh Kumar To: Anson Huang Cc: "robh+dt@kernel.org" , "mark.rutland@arm.com" , "shawnguo@kernel.org" , "s.hauer@pengutronix.de" , "kernel@pengutronix.de" , "festevam@gmail.com" , "catalin.marinas@arm.com" , "will.deacon@arm.com" , "rjw@rjwysocki.net" , Aisheng Dong , Daniel Baluta , Andy Gross , "horms+renesas@verge.net.au" , "heiko@sntech.de" , "arnd@arndb.de" , "bjorn.andersson@linaro.org" , "jagan@amarulasolutions.com" , "enric.balletbo@collabora.com" , "marc.w.gonzalez@free.fr" , "olof@lixom.net" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-pm@vger.kernel.org" , dl-linux-imx Subject: Re: [PATCH 3/3] cpufreq: imx-sc: add i.mx system controller cpufreq support Message-ID: <20190213101502.v75d3nfwctcks2gx@vireshk-i7> References: <1550027011-7884-1-git-send-email-Anson.Huang@nxp.com> <1550027011-7884-3-git-send-email-Anson.Huang@nxp.com> <20190213070904.3oswrjafy6cqedsr@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180323-120-3dd1ac Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13-02-19, 08:53, Anson Huang wrote: > Forgot to mention, i.MX system controller cpufreq actually can NOT do any CPU > clock/voltage scaling from Linux kernel, they are controlled by system controller > firmware and ONLY can be requested via RPC with secure mode, so Linux kernel > has to call SMC and trap to ARM-Trusted-Firmware to do it, in this case, is cpufreq-dt > still suitable to support it? I saw cpufreq-dt driver will do CPU clock/voltage scaling > directly. What about moving those SMC calls to the clk-driver, then it wouldn't matter to the cpufreq driver on how the clock is getting changed. -- viresh