On Tue, Mar 04, 2014 at 02:01:36PM +, Russell King - ARM Linux wrote:
> On Tue, Mar 04, 2014 at 02:54:52PM +0100, Andrew Lunn wrote:
> > > > 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, Seb
On Tue, Mar 04, 2014 at 03:02:25PM +0100, Sebastian Hesselbarth wrote:
> On 03/04/2014 02:53 PM, Jason Cooper wrote:
> >On Tue, Mar 04, 2014 at 12:11:36PM +, 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, A
On 03/04/2014 02:53 PM, Jason Cooper wrote:
On Tue, Mar 04, 2014 at 12:11:36PM +, 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 pat
On Tue, Mar 04, 2014 at 02:54:52PM +0100, Andrew Lunn wrote:
> > > 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...
>
> I doubt i will be doing anything with
> > 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...
I doubt i will be doing anything with it for the remainder of this
cycle. I would like to finish converting kir
On Tue, Mar 04, 2014 at 12:11:36PM +, 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 t
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,
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, S
> 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? i
On Mon, Mar 03, 2014 at 05:24:06PM -0500, Jason Cooper wrote:
> I've no issue with reverting this driver. I'll ask arm-soc to hold off
> on pulling the latest mvebu DT pull request which contains the DT node.
> I _really_ don't want to do a revert of a revert of a revert. :-/
Done. I'll work on
On Mon, Mar 03, 2014 at 06:15:30PM +, Russell King - ARM Linux wrote:
> On Mon, Mar 03, 2014 at 06:37:40PM +0100, Andrew Lunn wrote:
> > On Mon, Mar 03, 2014 at 03:02:15PM +, Russell King - ARM Linux wrote:
> > > On Mon, Feb 17, 2014 at 08:00:36PM +, Jason Cooper wrote:
> > > > The corr
On Mon, Mar 03, 2014 at 06:37:40PM +0100, Andrew Lunn wrote:
> On Mon, Mar 03, 2014 at 03:02:15PM +, Russell King - ARM Linux wrote:
> > On Mon, Feb 17, 2014 at 08:00:36PM +, Jason Cooper wrote:
> > > The corresponding driver didn't make it into v3.14, so we need to remove
> > > the node.
On Mon, Mar 03, 2014 at 03:02:15PM +, Russell King - ARM Linux wrote:
> On Mon, Feb 17, 2014 at 08:00:36PM +, 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.
>
On Mon, Feb 17, 2014 at 08:00:36PM +, 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
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.
Signed-off-by: Jason Cooper
---
Changes from v1:
- removed the reference to pmu_i
15 matches
Mail list logo
