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=-8.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable 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 DC7C4C43603 for ; Mon, 16 Dec 2019 04:05:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A6AE622B48 for ; Mon, 16 Dec 2019 04:05:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="HchpIwQM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726705AbfLPEFj (ORCPT ); Sun, 15 Dec 2019 23:05:39 -0500 Received: from mail-pf1-f195.google.com ([209.85.210.195]:36498 "EHLO mail-pf1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726719AbfLPEFg (ORCPT ); Sun, 15 Dec 2019 23:05:36 -0500 Received: by mail-pf1-f195.google.com with SMTP id x184so4854637pfb.3 for ; Sun, 15 Dec 2019 20:05:35 -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=d4XspCOLY0K+C1Vfb2PDWcaWLInJRK+f1WKwR2zrrME=; b=HchpIwQMnBNKqHOnvMjOMVaASy6pIUbbRENB4Er0WySYNfH+cBpQd/VVttcEc1iKxU S1PRRWmCeQcvQ71kCjxcxw41+AUwXVn06ggSP/Zx9ly0DoKdBGTHyVbF0ccUKPnpjHM+ xX3YY+c/v+G56ALgVfZqfy5qyUXDan07Mw01WG8VVtLiAxZf3yM10dpMJQx5B+lGuXdA hydKasR+2Z/bXmU6U1hqBFvb0IYLydzNSl3ZU39fzdqrbkMJDNWsewQly1buzzFbWPFk ielGKUyIRolOQcCwzMA3Dslc650R54M64soVcZ6fdMEva18UuIe1odrXveTbZJmYsueA Ga0w== 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=d4XspCOLY0K+C1Vfb2PDWcaWLInJRK+f1WKwR2zrrME=; b=alI+H6DHN+XAJ6wucIGdFMPN+TmVkPgv2gY3N+L9lmlqdlvboePosrCTbWt/cq7aHA XVxkEgzgdWwSky8Fi86k9GBT7jcKVmQrjdKJY0OFvkCyrx15VUax1/gnmRWquGqZRlHZ 6/mLUlrws0BOYoSU6YUhxkaMwjLlOHIisNtop36uzGtzqYCxbKQNmMfcXgIoYONqVUuS hD9YbAuZqlbUffqSINQBKBIL9wxAkjj+etQldTo7ft7zq/F6uv0gTPnubMAGjlCNH9yJ 2As4iIJz46/zMdZpbbHLw4lhLXSPDs3zRd2O1PPxhZMexh0WSR5cMV5tBiv8a7j1UQTx g9lg== X-Gm-Message-State: APjAAAXIuxvNH6VBKFl++zYpNMJpEV+fttDJiiW9BleR0231hVi6CPRi 3+4vLr1Q2BFYYpvuF1elV8Gw9w== X-Google-Smtp-Source: APXvYqwLt7wj56FeIgG9ZelBz/Zll/j8P4bcApK8Q+7U541auajpxb17fqK7nFsQ5ScZhkF9BwftfQ== X-Received: by 2002:a65:66d7:: with SMTP id c23mr16106550pgw.40.1576469135086; Sun, 15 Dec 2019 20:05:35 -0800 (PST) Received: from localhost ([122.171.234.168]) by smtp.gmail.com with ESMTPSA id e10sm20480322pfm.3.2019.12.15.20.05.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Dec 2019 20:05:34 -0800 (PST) Date: Mon, 16 Dec 2019 09:35:32 +0530 From: Viresh Kumar To: Dmitry Osipenko Cc: Thierry Reding , Jonathan Hunter , Peter De Schrijver , Prashant Gaikwad , "Rafael J. Wysocki" , Michael Turquette , Stephen Boyd , Peter Geis , Nicolas Chauvet , Marcel Ziswiler , linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 07/11] cpufreq: dt-platdev: Blacklist NVIDIA Tegra20 and Tegra30 SoCs Message-ID: <20191216040532.mzdovqoub5rdztwb@vireshk-i7> References: <20191118164512.8676-1-digetx@gmail.com> <20191118164512.8676-8-digetx@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191118164512.8676-8-digetx@gmail.com> User-Agent: NeoMutt/20180716-391-311a52 Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org On 18-11-19, 19:45, Dmitry Osipenko wrote: > Both NVIDIA Tegra20 and Tegra30 SoCs should be blacklisted because CPU > OPPs use supported_hw and thus platdev isn't suitable for these SoCs. > Currently cpufreq-dt driver produces a bit annoying warning splats > during boot because valid OPPs are not found, this will be fixed once > tegra20-cpufreq driver will be update to support cpufreq-dt. The warnings > will also happen on older stable kernels using newer device-trees, thus > this patch should be backported to stable kernels as well. > > Cc: > Reported-by: Jon Hunter > Fixes: 4053aa65c517 ("ARM: tegra: cardhu-a04: Add CPU Operating Performance Points") > Signed-off-by: Dmitry Osipenko > --- > drivers/cpufreq/cpufreq-dt-platdev.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c > index f1d170dcf4d3..aba591d57c67 100644 > --- a/drivers/cpufreq/cpufreq-dt-platdev.c > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c > @@ -121,6 +121,8 @@ static const struct of_device_id blacklist[] __initconst = { > { .compatible = "mediatek,mt8176", }, > { .compatible = "mediatek,mt8183", }, > > + { .compatible = "nvidia,tegra20", }, > + { .compatible = "nvidia,tegra30", }, > { .compatible = "nvidia,tegra124", }, > { .compatible = "nvidia,tegra210", }, Acked-by: Viresh Kumar -- viresh