linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/omap4: add twd clock to DT
Date: Tue, 20 May 2014 07:49:28 -0700	[thread overview]
Message-ID: <20140520144928.GB27830@atomide.com> (raw)
In-Reply-To: <537B19F1.5040907@ti.com>

* Tero Kristo <t-kristo@ti.com> [140520 02:01]:
> On 05/19/2014 07:27 PM, Tony Lindgren wrote:
> >* Joachim Eastwood <manabian@gmail.com> [140519 09:24]:
> >>On 19 May 2014 18:13, Tony Lindgren <tony@atomide.com> wrote:
> >>>* Joachim Eastwood <manabian@gmail.com> [140518 05:08]:
> >>>>On 22 April 2014 14:39, Tero Kristo <t-kristo@ti.com> wrote:
> >>>>>On 04/20/2014 07:22 PM, Gilles Chanteperdrix wrote:
> >>>>>>
> >>>>>>Le 19/04/2014 00:39, Tony Lindgren a ?crit :
> >>>>>>>
> >>>>>>>* Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> [140407 13:09]:
> >>>>>>>>
> >>>>>>>>Booting Linux 3.14 on Pandaboard currently gets the following
> >>>>>>>>message displayed:
> >>>>>>>>
> >>>>>>>>smp_twd: clock not found -2
> >>>>>>>>
> >>>>>>>>Define "mpu_periphclk" as the twd clock in omap4 dts to avoid this.
> >>>>>>>
> >>>>>>>
> >>>>>>>Tero, care to ack?
> >>>>>>
> >>>>>>
> >>>>>>Sorry if I did not mail the right people, get_maintainer.pl gave me a
> >>>>>>long list, and I did not feel like spamming all these people for such a
> >>>>>>small patch. I do not believe Tero was in this list.
> >>>>>>
> >>>>>>Regards.
> >>>>>
> >>>>>
> >>>>>Yea I don't think this is my expertise area, however the patch looks good to
> >>>>>me, so if you really need it:
> >>>>>
> >>>>>Acked-by: Tero Kristo <t-kristo@ti.com>
> >>>>
> >>>>Tony, care to add this to your omap 3.16 dt branch?
> >>>>
> >>>>I am still getting:
> >>>>[ 0.000152] smp_twd: clock not found -2
> >>>>
> >>>>So this fix from Gilles would be nice to have.
> >>>
> >>>Best that Tero picks this one up along with the other dt clock changes
> >>>he's queueing.
> >>
> >>I kinda assumed you would take it since you asked Tero to ack it. But
> >>either way is fine :)
> >
> >Yes that was before Tero started collecting the dt clock patches :)
> 
> I wouldn't say this to be a clock patch as such, this touches the driver
> behavior, i.e. registers the correct clock for the driver. That being said,
> I can still queue this up with the clock patches if that is what you want.

Yes please go ahead and take this one.

Thanks,

Tony

  reply	other threads:[~2014-05-20 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 20:05 [PATCH] arm/omap4: add twd clock to DT Gilles Chanteperdrix
2014-04-18 22:39 ` Tony Lindgren
2014-04-20 16:22   ` Gilles Chanteperdrix
2014-04-22 12:39     ` Tero Kristo
2014-05-18 12:08       ` Joachim Eastwood
2014-05-19 16:13         ` Tony Lindgren
2014-05-19 16:23           ` Joachim Eastwood
2014-05-19 16:27             ` Tony Lindgren
2014-05-20  9:01               ` Tero Kristo
2014-05-20 14:49                 ` Tony Lindgren [this message]
2014-05-23 10:57                   ` Tero Kristo

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=20140520144928.GB27830@atomide.com \
    --to=tony@atomide.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).