Linux RTC
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Roman Yeryomin <roman@advem.lv>,
	Hans Ulli Kroll <ulli.kroll@googlemail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Felix Fietkau <nbd@openwrt.org>,
	"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Russell King <rmk+kernel@arm.linux.org.uk>
Subject: [rtc-linux] Re: Gemini Soc timers
Date: Sun, 12 Jul 2015 23:06:03 +0200	[thread overview]
Message-ID: <9777530.lnQDW33Iqo@wuerfel> (raw)
In-Reply-To: <CACRpkdbf2CfT7fJ6wAC3WB9=-Cp0A5xZAO1-Rh78o-U26Fr0Ag@mail.gmail.com>

On Friday 10 July 2015 10:48:26 Linus Walleij wrote:
> On Thu, Jul 9, 2015 at 6:48 PM, Roman Yeryomin <roman@advem.lv> wrote:
> > [Me]
> >> As usual they are just keeping it out of mainline, and this
> >> is adding sched_clock() and other goodies so should
> >> probably be upstreamed ASAP.
> >
> >
> > This is what I initially submitted here.
> 
> Ah. I missed part of the start of the discussion it seems.
> 
> > But Arnd wanted to see a smaller patch which only fixes gemini timer issue
> > (t.i. shed clock being 100Hz instead of 25MHz).
> > Also I've submitted 4.1 support yesterday, but patches didn't change much
> > comparing to 3.18
> 
> On the other hand I think the bigger patch is OK actually.
> 
> I rewrote the timer support some time back and did not get
> anyone to test it properly at the time, so the patch went in
> untested. So this is a fix.

The bigger patch seemed a little too verbose to have it backported
to stable kernels, so I asked for a minimal fix that could be marked
as stable, with the other changes applied on top for the current
arm-soc tree.

I'm still on parental leave and not dealing with patches directly,
so whichever patch we want should get routed through Ulli to arm@kernel.org

	Arnd

-- 
-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2015-07-12 21:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 15:08 [1/2] RTC: Add core rtc support for Gemini Soc devices Hans Ulli Kroll
2015-05-01 23:42 ` [rtc-linux] " Alexandre Belloni
2015-05-06  9:39   ` Arnd Bergmann
2015-05-06  9:53     ` Alexandre Belloni
2015-05-06 16:21       ` Roman Yeryomin
2015-05-06 19:22         ` Arnd Bergmann
2015-05-07  9:03           ` Roman Yeryomin
2015-05-07 17:35             ` Hans Ulli Kroll
2015-05-07 21:31               ` Roman Yeryomin
2015-05-08 16:08             ` Arnd Bergmann
2015-07-08 22:29               ` Roman Yeryomin
2015-07-09  8:04                 ` Arnd Bergmann
2015-07-09 11:58                   ` 'Hans Ulli Kroll' via rtc-linux
2015-07-09 13:02                     ` [rtc-linux] Gemini Soc timers Roman Yeryomin
2015-07-09 15:48                       ` [rtc-linux] " Linus Walleij
2015-07-09 16:48                         ` Roman Yeryomin
2015-07-10  8:48                           ` Linus Walleij
2015-07-12 21:06                             ` Arnd Bergmann [this message]
2015-07-09 16:51                   ` [rtc-linux] Re: [1/2] RTC: Add core rtc support for Gemini Soc devices Roman Yeryomin
2015-07-19 16:28                     ` 'Hans Ulli Kroll' via rtc-linux
2015-05-07  3:00     ` Hans Ulli Kroll
2015-05-07  7:49       ` Arnd Bergmann
2015-05-07 17:46         ` Hans Ulli Kroll
2015-05-07 21:35           ` Roman Yeryomin
2015-05-08 18:28             ` Hans Ulli Kroll

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=9777530.lnQDW33Iqo@wuerfel \
    --to=arnd@arndb.de \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd@openwrt.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=roman@advem.lv \
    --cc=rtc-linux@googlegroups.com \
    --cc=ulli.kroll@googlemail.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