From mboxrd@z Thu Jan 1 00:00:00 1970 From: Soren Brinkmann Subject: [PATCH 0/2] clockevents Date: Mon, 9 Dec 2013 16:34:44 -0800 Message-ID: <1386635686-15686-1-git-send-email-soren.brinkmann@xilinx.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Daniel Lezcano , Thomas Gleixner Cc: Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell , Russell King , Michal Simek , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, =?UTF-8?q?S=C3=B6ren=20Brinkmann?= List-Id: devicetree@vger.kernel.org Hi Thomas, before respinning the complete series, I thought we could take a look a= t the changes to the timer core, since I expect them to need to be refine= d for an actual submission. The first patch is the patch you proposed to serialize callers of clockevents_update_freq(). I guess you may find some better words to describe your changes. I found it not that easy to find a nice description for somebody else's patch. The second patch is my shot at extending clockevents_update_freq() to also handle timers in periodic mode. In my approach I assume that simply calling the timer's 'set_mode()' API takes care of programming a= n appropriate interval based on the current timer frequency. If that doesn't work for all timers, I guess it would require a new API call. O= r I just missed some other way. Thanks, S=C3=B6ren Soren Brinkmann (2): time: Serialize calls to 'clockevents_update_freq' in the timing core time: clockevents: Adjust timer interval when frequency changes kernel/time/clockevents.c | 32 +++++++++++++++++++++++++------- kernel/time/tick-broadcast.c | 25 +++++++++++++++++++------ kernel/time/tick-internal.h | 4 ++++ 3 files changed, 48 insertions(+), 13 deletions(-) --=20 1.8.5.1