linux-kernel - Re: [PATCH v3 3/3] memory: tegra124-emc: Add EMC driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <53FB77F5.3010604@wwwdotorg.org>
Date:	Mon, 25 Aug 2014 11:52:53 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Tomeu Vizoso <tomeu.vizoso@...labora.com>,
	Pavel Machek <pavel@....cz>,
	Thierry Reding <thierry.reding@...il.com>
CC:	linux-pm@...r.kernel.org,
	Terje Bergström <tbergstrom@...dia.com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Len Brown <len.brown@...el.com>, linux-tegra@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
	Mikko Perttunen <mperttunen@...dia.com>
Subject: Re: [PATCH v3 3/3] memory: tegra124-emc: Add EMC driver

On 08/19/2014 03:06 AM, Tomeu Vizoso wrote:
> On 19 August 2014 11:03, Pavel Machek <pavel@....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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/