From: Stephen Warren <swarren@wwwdotorg.org>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Pavel Machek <pavel@ucw.cz>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pm@vger.kernel.org,
"Terje Bergström" <tbergstrom@nvidia.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <len.brown@intel.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
"Javier Martinez Canillas" <javier.martinez@collabora.co.uk>,
"Mikko Perttunen" <mperttunen@nvidia.com>
Subject: Re: [PATCH v3 3/3] memory: tegra124-emc: Add EMC driver
Date: Mon, 25 Aug 2014 11:52:53 -0600 [thread overview]
Message-ID: <53FB77F5.3010604@wwwdotorg.org> (raw)
In-Reply-To: <CAAObsKA+JofL3JANtdqAqGgtA3-x+GMQ0Ei7gMzmmWynP3U9Sg@mail.gmail.com>
On 08/19/2014 03:06 AM, Tomeu Vizoso wrote:
> On 19 August 2014 11:03, Pavel Machek <pavel@ucw.cz> wrote:
>> On Tue 2014-08-19 10:38:43, Tomeu Vizoso wrote:
>>> Sets the EMC clock rate based on the bandwidth requirements registered by
>>> memory clients through the PM_QOS_MEMORY_BANDWIDTH class.
>>>
>>> Note: this is just an example and not a proper driver for a external memory
>>> controller. Its only purpose is to illustrate how such a driver
>>> would set the
>>
>> So... you don't want this to be merged?
>
> Not really, there's quite some work left to do until we have a proper
> EMC driver for Tegra124.
Given that, the only patches in this series that should be merged touch
(a) pm_qos, (b) tegradrm. As such, I would suggest that patch 1 be
merged into the pm_qos tree in a standalone topic branch, and Thierry
can merge this into the Tegra tree and apply patch 2 when he's ready.
Since patch 3 is the only patch that would normally go through the Tegra
tree, and patch 3 isn't to be applied yet, I don't intend on applying
any of these patches to the Tegra tree.
prev parent reply other threads:[~2014-08-25 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 8:38 [PATCH v3 0/3] PM QoS: Add support for memory bandwidth constraints Tomeu Vizoso
2014-08-19 8:38 ` [PATCH v3 1/3] PM / QoS: Add PM_QOS_MEMORY_BANDWIDTH class Tomeu Vizoso
2014-08-19 8:38 ` [PATCH v3 2/3] drm/tegra: Request memory bandwidth for the display controller Tomeu Vizoso
2014-08-19 9:02 ` Pavel Machek
2014-08-19 8:38 ` [PATCH v3 3/3] memory: tegra124-emc: Add EMC driver Tomeu Vizoso
2014-08-19 9:03 ` Pavel Machek
2014-08-19 9:06 ` Tomeu Vizoso
2014-08-25 17:52 ` Stephen Warren [this message]
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=53FB77F5.3010604@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=javier.martinez@collabora.co.uk \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=tbergstrom@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=tomeu.vizoso@collabora.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox