Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751710AbdISWgw (ORCPT ); Tue, 19 Sep 2017 18:36:52 -0400 Received: from mail-pf0-f174.google.com ([209.85.192.174]:55923 "EHLO mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751651AbdISWgr (ORCPT ); Tue, 19 Sep 2017 18:36:47 -0400 X-Google-Smtp-Source: AOwi7QB5AzKnlkfUskt0DdTZXMT6XEKPyaK05cx35kNxWIP0XjaFGZhMTQyGsl+Vx6nlj4rVm438Sw== Date: Tue, 19 Sep 2017 15:36:45 -0700 From: Viresh Kumar To: Dave Gerlach Cc: sunil.m@techveda.org, rjw@rjwysocki.net, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, karthik@techveda.org Subject: Re: [PATCH v2] drivers: cpufreq: Fix sysfs duplicate filename creation for platform-device Message-ID: <20170919223645.GD30848@ubuntu> References: <20170918011503.GA17030@ubuntu> <1505762285-16161-1-git-send-email-sunil.m@techveda.org> <8a57f05a-598f-440e-f8d0-ddde5627d075@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8a57f05a-598f-440e-f8d0-ddde5627d075@ti.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: 1162 Lines: 27 On 19-09-17, 10:12, Dave Gerlach wrote: > Hi, > On 09/18/2017 02:18 PM, sunil.m@techveda.org wrote: > > From: Suniel Mahesh > > > > ti-cpufreq and cpufreq-dt-platdev drivers are registering platform-device > > with same name "cpufreq-dt" using platform_device_register_*() routines. > > This is leading to build warnings appended below. > > > > Providing hardware information to OPP framework along with the platform- > > device creation should be done by ti-cpufreq driver before cpufreq-dt > > driver comes into place. > > > > This patch add's TI SoC am33xx (uses opp-v2 property) in the blacklist of > > devices in cpufreq-dt-platform driver to avoid creating platform-device > > twice and remove build warnings (suggested by Viresh Kumar). > > This looks good to me, but this also affects "ti,am43" and "ti,dra7" platforms, > care to add those to the blacklist as well with this patch? Thanks. Also please rebase on top of the pm/linux-next branch as I have pushed a similar patch there. (Actually its applied to pm/bleeding-edge branch for now and may take a day to get to pm/linux-next. You can wait in that case.). -- viresh