linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: Gemini Soc timers
Date: Thu, 9 Jul 2015 17:48:45 +0200	[thread overview]
Message-ID: <CACRpkdYm-W8FqBgvustJUweizocmX9LtVS6Q=7j8EjF8D+H77Q@mail.gmail.com> (raw)
In-Reply-To: <5e6214ee669fbd797ad2ef257ce52068@advem.lv>

On Thu, Jul 9, 2015 at 3:02 PM, Roman Yeryomin <roman@advem.lv> wrote:
> On 2015-07-09 14:58, Hans Ulli Kroll wrote:
>>
>> Hi
>>
>> On Thu, 9 Jul 2015, Arnd Bergmann wrote:
>>
>>> On Thursday 09 July 2015 01:29:39 Roman Yeryomin wrote:
>>> >
>>> > OK, here are the minimal changes required (see attachment). Tested on
>>> > 4.1.1
>>> > Let me know if you want me to submit it in some other way.
>>> >
>>>
>>> The changes look ok to me. Please submit them as two separate
>>> patches (1. set up and use timer3, 2. register sched_clock) according
>>> to the Documentation/SubmittingPatches description.
>>>
>>> Thanks,
>>>
>>>         Arnd
>>>
>>
>> have you seen this thread ...
>> [PATCH 00/18] ARM: Migrate clockevent drivers to 'set-state
>> http://permalink.gmane.org/gmane.linux.ports.arm.kernel/423992
>>
>> arch/arm/mach-gemini/time.c              | 69 ++++++++++++------------
>>
>> Two or more weeks ago I send a patchset fixing this problem.
>> At this time Arnd was in holiday and until today I was very busy at work.
>
>
> Sorry, I didn't see your patches.
> Arnd requested minimal changes and until yesterday I was very busy too.
>
>> I can rework my patches on top of Viresh's patchset
>
>
> It looks that this patchset doesn't conflict with the fix needed.

Can any of you guys just look at this thing from OpenWRT:
http://git.openwrt.org/?p=openwrt.git;a=blob;f=target/linux/gemini/patches-3.18/160-gemini-timers.patch;h=4b0edb45d162f751bfb7475f5b3158f28d69fe84;hb=HEAD

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.

Yours,
Linus Walleij

  parent reply	other threads:[~2015-07-09 15:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 15:08 [PATCH 0/2] ARM: Gemini: add RTC support for Gemini SoC Hans Ulli Kroll
2010-12-14 15:08 ` [PATCH 1/2] RTC: Add core rtc support for Gemini Soc devices Hans Ulli Kroll
2015-05-01 23:42   ` [1/2] " 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
     [not found]                       ` <5e6214ee669fbd797ad2ef257ce52068@advem.lv>
2015-07-09 15:48                         ` Linus Walleij [this message]
2015-07-09 16:48                           ` Gemini Soc timers Roman Yeryomin
2015-07-10  8:48                             ` Linus Walleij
2015-07-12 21:06                               ` Arnd Bergmann
2015-07-09 16:51                     ` [1/2] RTC: Add core rtc support for Gemini Soc devices Roman Yeryomin
2015-07-19 16:28                       ` Hans Ulli Kroll
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
2010-12-14 15:08 ` [PATCH 2/2] ARM: Gemini: add platform support for Gemini RTC Hans Ulli Kroll
2011-01-07  9:31 ` [PATCH 0/2] ARM: Gemini: add RTC support for Gemini SoC Russell King - ARM Linux
2011-01-07 14:47   ` Hans Ulli Kroll
2011-01-19 11:07   ` Russell King - ARM Linux
2011-01-24 17:22     ` Russell King - ARM Linux

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='CACRpkdYm-W8FqBgvustJUweizocmX9LtVS6Q=7j8EjF8D+H77Q@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --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).