From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Tetsuyuki Kobayashi <koba@kmckk.co.jp>,
SH-Linux <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] ARM: shmobile: emev2: add PMU information to emev2.dtsi
Date: Wed, 31 Jul 2013 16:33:21 +0900 [thread overview]
Message-ID: <20130731073320.GH5090@verge.net.au> (raw)
In-Reply-To: <CANqRtoTVVp5xY7monC6c87Ni=pS5dNG=fS_isAg3qZNQCzaNNg@mail.gmail.com>
On Wed, Jul 31, 2013 at 04:11:23PM +0900, Magnus Damm wrote:
> Hi Simon,
>
> On Wed, Jul 31, 2013 at 4:05 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Wed, Jul 31, 2013 at 03:39:04PM +0900, Simon Horman wrote:
> >> On Wed, Jul 24, 2013 at 12:42:40PM +0900, Magnus Damm wrote:
> >> > From: Magnus Damm <damm@opensource.se>
> >> >
> >> > Add PMU information to emev2.dtsi. With this
> >> > included KZM9D DT reference may use the PMU.
> >>
> >> Thanks, I will queue this up for v3.12 in the dt2 branch.
> >
> > When booting a debian armel userspace with this patch applied on top of
> > renesas-devel-20130731 I see the following.
> >
> > I do not observe this problem with the sh73a0 or r8a7740 versions
> > of this patch applied, though I assume that in the case of the r8a7740
> > that is because it is UP.
>
> Looks like the STI clockevent rating patch is missing. SMP operation
> of EMEV2 is broken without that patch.
Thanks, that patch resolves the problem that I was seeing.
I'll put it into devel for now in topic/em_sti.
topic/ indicating that is isn't queued-up yet as
I'd like to give the clocksource people a chance to review it.
prev parent reply other threads:[~2013-07-31 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 3:42 Magnus Damm
2013-07-31 6:39 ` Simon Horman
2013-07-31 7:05 ` Simon Horman
2013-07-31 7:11 ` Magnus Damm
2013-07-31 7:33 ` Simon Horman [this message]
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=20130731073320.GH5090@verge.net.au \
--to=horms@verge.net.au \
--cc=koba@kmckk.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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
all inboxes | Powered by JetHome®