Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752067AbdIMTSn (ORCPT ); Wed, 13 Sep 2017 15:18:43 -0400 Received: from mail-pg0-f47.google.com ([74.125.83.47]:46721 "EHLO mail-pg0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751880AbdIMTSm (ORCPT ); Wed, 13 Sep 2017 15:18:42 -0400 X-Google-Smtp-Source: ADKCNb5GhXzlV6u1Nhf2EF7Nrr/hatOmEKrRItmFmvk6Q1C1DaaYJ4HtHzVFwRMO+K4B8fjwhltsrQ== Date: Wed, 13 Sep 2017 12:18:40 -0700 From: Viresh Kumar To: Andy Yan Cc: rjw@rjwysocki.net, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, heiko@sntech.de Subject: Re: [PATCH 2/2] cpufreq: dt: add support for rockchip rv1108 Message-ID: <20170913191840.GB11836@ubuntu> References: <1503306404-28876-1-git-send-email-andy.yan@rock-chips.com> <1503306624-28937-1-git-send-email-andy.yan@rock-chips.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1503306624-28937-1-git-send-email-andy.yan@rock-chips.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 981 Lines: 28 On 21-08-17, 17:10, Andy Yan wrote: > Add the compatible string to support the generic device tree > cpufreq-dt driver on rockchip rv1108 soc. > > Signed-off-by: Andy Yan > --- > > drivers/cpufreq/cpufreq-dt-platdev.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c > index 1c26292..2d71c09 100644 > --- a/drivers/cpufreq/cpufreq-dt-platdev.c > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c > @@ -69,6 +69,7 @@ static const struct of_device_id machines[] __initconst = { > { .compatible = "renesas,r8a7794", }, > { .compatible = "renesas,sh73a0", }, > > + { .compatible = "rockchip,rv1108", }, > { .compatible = "rockchip,rk2928", }, > { .compatible = "rockchip,rk3036", }, > { .compatible = "rockchip,rk3066a", }, You use operating-points-v2 or the V1 bindings for this SoC? The SoCs using operating-points-v2 don't need such changes anymore. -- viresh