From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: [PATCH 00/10] Orion Watchdog fixes Date: Tue, 16 Jul 2013 08:59:52 +0200 Message-ID: <20130716065952.GA25043@lunn.ch> References: <1373931163-12670-1-git-send-email-ezequiel.garcia@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1373931163-12670-1-git-send-email-ezequiel.garcia@free-electrons.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Ezequiel Garcia Cc: Lior Amsalem , Andrew Lunn , linux-watchdog@vger.kernel.org, Arnd Bergmann , devicetree-discuss@lists.ozlabs.org, wim@iguana.be, Maen Suleiman , Thomas Petazzoni , Gregory Clement , Jason Cooper , linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth List-Id: devicetree@vger.kernel.org On Mon, Jul 15, 2013 at 08:32:33PM -0300, Ezequiel Garcia wrote: > This patchset introduces a bunch of fixes that removes the direct use of > the shared timer control register, and also removes the need to include > a mach-specific header. > > With this changes the driver can be included in multiplatforms builds, > and in particular be used for the Armada 370/XP SoC. Hi Ezequiel Maybe i'm missing something here. You are making use of orion_timer_ctrl_clrset() from time-orion.c. How will this work on 370/XP which has a different clocksource driver? Thanks Andrew