[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5315AD6F.1070804@gmail.com>
Date: Tue, 04 Mar 2014 11:39:43 +0100
From: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To: Andrew Lunn <andrew@...n.ch>, Jason Cooper <jason@...edaemon.net>
CC: Russell King - ARM Linux <linux@....linux.org.uk>,
Sebastian Hesselbarth <sebastian.hesselbarth@...glemail.com>,
linux-kernel@...r.kernel.org,
Gregory CLEMENT <gregory.clement@...e-electrons.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH V2] ARM: dove: dt: revert PMU interrupt controller node
On 03/04/2014 10:26 AM, Andrew Lunn wrote:
>> I could have sworn this was discussed with this particular patchset, but
>> I'm unable to find the conversation in my archives. Neither during the
>> patch submission process, nor the (long) pull request thread.
>>
>> Perhaps it was an irc conversation? Andrew, Sebastian, can you find a
>> link? iirc, one of the DT maintainers (Mark Rutland?) raised the same
>> concern and I thought we answered that sufficiently...
>
> It was the cpufreq driver which caused the discussion. I looked at it
> for a while, and then task swapped onto the kirkwood move into
> mach-mvebu.
I guess you are looking for this discussion
http://comments.gmane.org/gmane.linux.power-management.general/41053
and specifically Mark's remarks on PMU and DT in here
http://permalink.gmane.org/gmane.linux.ports.arm.kernel/285384
BTW, +1 for a single PMU node that either serves an mfd (or type
of) driver or that subsystem drivers derive their resources from.
Looking at Dove FS, that would also include clock gating, which
could be a mess to sort out.. anyway, let's get it on.
Sebastian
--
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/
Powered by blists - more mailing lists