From: Viresh Kumar <viresh.kumar@linaro.org>
To: Dave Gerlach <d-gerlach@ti.com>
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
Date: Tue, 19 Sep 2017 15:36:45 -0700 [thread overview]
Message-ID: <20170919223645.GD30848@ubuntu> (raw)
In-Reply-To: <8a57f05a-598f-440e-f8d0-ddde5627d075@ti.com>
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 <sunil.m@techveda.org>
> >
> > 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
next prev parent reply other threads:[~2017-09-19 22:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 18:34 [PATCH] drivers: cpufreq: Fix sysfs duplicate filename creation for platform-device sunil.m
2017-09-18 1:15 ` Viresh Kumar
2017-09-18 16:59 ` Suniel Mahesh
2017-09-18 19:18 ` [PATCH v2] " sunil.m
2017-09-19 15:12 ` Dave Gerlach
2017-09-19 15:12 ` Dave Gerlach
2017-09-19 22:36 ` Viresh Kumar [this message]
2017-09-20 4:16 ` Suniel Mahesh
2017-09-21 13:39 ` [PATCH v3] " sunil.m
2017-09-21 17:53 ` Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170919223645.GD30848@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=d-gerlach@ti.com \
--cc=karthik@techveda.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sunil.m@techveda.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.