From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Subject: Re: [PATCH v3 3/3] memory: tegra124-emc: Add EMC driver Date: Mon, 25 Aug 2014 11:52:53 -0600 Message-ID: <53FB77F5.3010604@wwwdotorg.org> References: <1408437523-8542-1-git-send-email-tomeu.vizoso@collabora.com> <1408437523-8542-4-git-send-email-tomeu.vizoso@collabora.com> <20140819090314.GC7862@amd> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-pm-owner@vger.kernel.org To: Tomeu Vizoso , Pavel Machek , Thierry Reding Cc: linux-pm@vger.kernel.org, =?UTF-8?B?VGVyamUgQmVyZ3N0csO2bQ==?= , "Rafael J. Wysocki" , Len Brown , linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, Javier Martinez Canillas , Mikko Perttunen List-Id: linux-tegra@vger.kernel.org On 08/19/2014 03:06 AM, Tomeu Vizoso wrote: > On 19 August 2014 11:03, Pavel Machek 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.