All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
	linux-kernel@vger.kernel.org,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2] ARM: dove: dt: revert PMU interrupt controller node
Date: Mon, 3 Mar 2014 18:37:40 +0100	[thread overview]
Message-ID: <20140303173740.GC16655@lunn.ch> (raw)
In-Reply-To: <20140303150215.GI21483@n2100.arm.linux.org.uk>

On Mon, Mar 03, 2014 at 03:02:15PM +0000, Russell King - ARM Linux wrote:
> On Mon, Feb 17, 2014 at 08:00:36PM +0000, Jason Cooper wrote:
> > The corresponding driver didn't make it into v3.14, so we need to remove
> > the node.  Dove systems fail to boot with the node present and no
> > driver.
> > 
> > This node will be re-added when the driver makes it to mainline.
> 
> I'm going to stick my oar in on this and ask what is a very fundamental
> question.
> 
> If we're adding the PMU interrupt controller as a separate "device"
> aren't we describing our implementation rather than the hardware?  It
> isn't a separate device as far as the description of it in the reference
> manuals.
> 
> Moreover, should the PMU interrupt controller be something which is
> handled by a separate chunk of code to a driver for the PMU as a whole,
> or are we storing up problems with resource clashes?  I can quite see
> a PMU driver coming along in the future offering a pair of generic
> power domains for the GPU and VPU, and such a driver would need to map
> all the PMU registers so it can access the power control, reset and
> isolator registers.

Hi Russell

I suspect you are right, we are storing up problems.

During the 4 months between submitting this driver and actually
getting it accepted, i've learned quite a bit. I tried to implement
cpufreq for Dove and ran into the problems you mention. The registers
in the PMU are interleaved so that you cannot cleanly separate out the
range needed for cpufreq. We probably need a PMU device, which exports
a register syscon and have the interrupt controller make use of it.

	Andrew

WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: dove: dt: revert PMU interrupt controller node
Date: Mon, 3 Mar 2014 18:37:40 +0100	[thread overview]
Message-ID: <20140303173740.GC16655@lunn.ch> (raw)
In-Reply-To: <20140303150215.GI21483@n2100.arm.linux.org.uk>

On Mon, Mar 03, 2014 at 03:02:15PM +0000, Russell King - ARM Linux wrote:
> On Mon, Feb 17, 2014 at 08:00:36PM +0000, Jason Cooper wrote:
> > The corresponding driver didn't make it into v3.14, so we need to remove
> > the node.  Dove systems fail to boot with the node present and no
> > driver.
> > 
> > This node will be re-added when the driver makes it to mainline.
> 
> I'm going to stick my oar in on this and ask what is a very fundamental
> question.
> 
> If we're adding the PMU interrupt controller as a separate "device"
> aren't we describing our implementation rather than the hardware?  It
> isn't a separate device as far as the description of it in the reference
> manuals.
> 
> Moreover, should the PMU interrupt controller be something which is
> handled by a separate chunk of code to a driver for the PMU as a whole,
> or are we storing up problems with resource clashes?  I can quite see
> a PMU driver coming along in the future offering a pair of generic
> power domains for the GPU and VPU, and such a driver would need to map
> all the PMU registers so it can access the power control, reset and
> isolator registers.

Hi Russell

I suspect you are right, we are storing up problems.

During the 4 months between submitting this driver and actually
getting it accepted, i've learned quite a bit. I tried to implement
cpufreq for Dove and ran into the problems you mention. The registers
in the PMU are interleaved so that you cannot cleanly separate out the
range needed for cpufreq. We probably need a PMU device, which exports
a register syscon and have the interrupt controller make use of it.

	Andrew

  reply	other threads:[~2014-03-03 17:38 UTC|newest]

Thread overview: 68+ 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-01-28 17:35       ` Jason Cooper
2014-02-04 18:59       ` Thomas Gleixner
2014-02-04 18:59         ` Thomas Gleixner
2014-02-04 19:05         ` Jason Cooper
2014-02-04 19:05           ` Jason Cooper
2014-02-04 21:12         ` Jason Cooper
2014-02-04 21:12           ` Jason Cooper
2014-02-04 21:30           ` Thomas Gleixner
2014-02-04 21:30             ` Thomas Gleixner
2014-02-07 18:08             ` Jason Cooper
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:24                 ` Jason Cooper
2014-02-17 19:32               ` [GIT PULL] irqchip: dove: drivers for v3.14 Jason Cooper
2014-02-17 19:32                 ` Jason Cooper
2014-02-18 20:51                 ` Thomas Gleixner
2014-02-18 20:51                   ` Thomas Gleixner
2014-02-19 15:18                   ` Jason Cooper
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-02-17 20:00                 ` Jason Cooper
2014-03-03 15:02                 ` Russell King - ARM Linux
2014-03-03 15:02                   ` Russell King - ARM Linux
2014-03-03 17:37                   ` Andrew Lunn [this message]
2014-03-03 17:37                     ` Andrew Lunn
2014-03-03 18:15                     ` Russell King - ARM Linux
2014-03-03 18:15                       ` Russell King - ARM Linux
2014-03-03 22:24                       ` Jason Cooper
2014-03-03 22:24                         ` Jason Cooper
2014-03-04  3:08                         ` 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-04  5:32                             ` Jason Cooper
2014-03-04 10:13                             ` [tip:irq/core] Revert irqchip: irq-dove: Add PMU interrupt controller tip-bot for Jason Cooper
2014-03-05  0:41                             ` [PATCH] Revert "irqchip: irq-dove: Add PMU interrupt controller." Russell King - ARM Linux
2014-03-05  0:41                               ` Russell King - ARM Linux
2014-03-05  9:24                               ` Andrew Lunn
2014-03-05  9:24                                 ` Andrew Lunn
2014-03-05 11:52                               ` Carlo Caione
2014-03-05 11:52                                 ` Carlo Caione
2014-03-05 14:42                               ` Thomas Gleixner
2014-03-05 14:42                                 ` Thomas Gleixner
2014-03-05 19:20                                 ` Russell King - ARM Linux
2014-03-05 19:20                                   ` Russell King - ARM Linux
2014-03-05 21:36                                   ` Thomas Gleixner
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  9:26                           ` Andrew Lunn
2014-03-04 10:39                           ` Sebastian Hesselbarth
2014-03-04 10:39                             ` Sebastian Hesselbarth
2014-03-04 12:11                             ` Russell King - ARM Linux
2014-03-04 12:11                               ` Russell King - ARM Linux
2014-03-04 13:53                               ` Jason Cooper
2014-03-04 13:53                                 ` Jason Cooper
2014-03-04 13:54                                 ` Andrew Lunn
2014-03-04 13:54                                   ` Andrew Lunn
2014-03-04 14:01                                   ` Russell King - ARM Linux
2014-03-04 14:01                                     ` Russell King - ARM Linux
2014-03-04 14:41                                     ` Andrew Lunn
2014-03-04 14:41                                       ` Andrew Lunn
2014-03-04 14:02                                 ` Sebastian Hesselbarth
2014-03-04 14:02                                   ` Sebastian Hesselbarth
2014-03-04 14:18                                   ` Jason Cooper
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=20140303173740.GC16655@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=sebastian.hesselbarth@googlemail.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.