From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: dove: dt: revert PMU interrupt controller node
Date: Tue, 04 Mar 2014 15:02:25 +0100 [thread overview]
Message-ID: <5315DCF1.90608@gmail.com> (raw)
In-Reply-To: <20140304135306.GL1872@titan.lakedaemon.net>
On 03/04/2014 02:53 PM, Jason Cooper wrote:
> On Tue, Mar 04, 2014 at 12:11:36PM +0000, Russell King - ARM Linux wrote:
>> On Tue, Mar 04, 2014 at 11:39:43AM +0100, Sebastian Hesselbarth wrote:
>>> 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.
>>
>> So we have cpufreq, pm domains and an irq controller. What's the plan
>> for this, who's going to look at sorting this out?
>
> Andrew, Sebastian? I'm currently task-saturated...
Phew, looks like I'll have to take it?
Are you guys ok with having a single PMU node with syscon provided
regmap and make all drivers depend on it? I'd like to get a go from
Russell here, as he has clearly something in mind.
We can consolidate drivers later if required. If we start that now,
we definitely risk running out of time for v3.15.
Sebastian
next prev parent reply other threads:[~2014-03-04 14:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 17:29 [GIT PULL] irqchip: dove: drivers for v3.14 Jason Cooper
2013-12-11 17:50 ` Jason Cooper
2014-01-10 18:34 ` Jason Cooper
2014-01-28 17:35 ` Jason Cooper
2014-02-04 18:59 ` Thomas Gleixner
2014-02-04 19:05 ` Jason Cooper
2014-02-04 21:12 ` Jason Cooper
2014-02-04 21:30 ` Thomas Gleixner
2014-02-07 18:08 ` Jason Cooper
2014-02-17 19:24 ` [RESEND PATCH] ARM: dove: dt: revert PMU interrupt controller node Jason Cooper
2014-02-17 19:32 ` [GIT PULL] irqchip: dove: drivers for v3.14 Jason Cooper
2014-02-18 20:51 ` Thomas Gleixner
2014-02-19 15:18 ` Jason Cooper
2014-02-17 20:00 ` [PATCH V2] ARM: dove: dt: revert PMU interrupt controller node Jason Cooper
2014-03-03 15:02 ` Russell King - ARM Linux
2014-03-03 17:37 ` Andrew Lunn
2014-03-03 18:15 ` Russell King - ARM Linux
2014-03-03 22:24 ` Jason Cooper
2014-03-04 3:08 ` Jason Cooper
2014-03-04 5:32 ` [PATCH] Revert "irqchip: irq-dove: Add PMU interrupt controller." Jason Cooper
2014-03-05 0:41 ` Russell King - ARM Linux
2014-03-05 9:24 ` Andrew Lunn
2014-03-05 11:52 ` Carlo Caione
2014-03-05 14:42 ` Thomas Gleixner
2014-03-05 19:20 ` Russell King - ARM Linux
2014-03-05 21:36 ` Thomas Gleixner
2014-03-04 9:26 ` [PATCH V2] ARM: dove: dt: revert PMU interrupt controller node Andrew Lunn
2014-03-04 10:39 ` Sebastian Hesselbarth
2014-03-04 12:11 ` Russell King - ARM Linux
2014-03-04 13:53 ` Jason Cooper
2014-03-04 13:54 ` Andrew Lunn
2014-03-04 14:01 ` Russell King - ARM Linux
2014-03-04 14:41 ` Andrew Lunn
2014-03-04 14:02 ` Sebastian Hesselbarth [this message]
2014-03-04 14:18 ` Jason Cooper
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=5315DCF1.90608@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).