From: Andrew Lunn <andrew@lunn.ch>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
linux-watchdog@vger.kernel.org,
Jason Cooper <jason@lakedaemon.net>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Arnd Bergmann <arnd@arndb.de>,
Lior Amsalem <alior@marvell.com>,
Maen Suleiman <maen@marvell.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
wim@iguana.be
Subject: Re: [PATCH 00/10] Orion Watchdog fixes
Date: Tue, 16 Jul 2013 08:59:52 +0200 [thread overview]
Message-ID: <20130716065952.GA25043@lunn.ch> (raw)
In-Reply-To: <1373931163-12670-1-git-send-email-ezequiel.garcia@free-electrons.com>
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
next prev parent reply other threads:[~2013-07-16 7:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 23:32 [PATCH 00/10] Orion Watchdog fixes Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 01/10] clocksource: orion: Add thread-safe API header Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 02/10] watchdog: orion: Use thread-safe clocksource API Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 03/10] watchdog: orion: Rename device-tree binding documentation Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 04/10] watchdog: orion: Use the proper watchdog register Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 05/10] watchdog: orion: Add a memory resource for RSTOUT register Ezequiel Garcia
2013-07-16 14:04 ` Andrew Lunn
2013-07-16 14:18 ` Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 06/10] watchdog: orion: Update device-tree binding documentation Ezequiel Garcia
2013-07-16 13:24 ` Jason Cooper
2013-07-15 23:32 ` [PATCH 07/10] watchdog: orion: Remove unneeded BRIDGE_CAUSE clear Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 08/10] watchdog: orion: Remove mach-specific unneeded header Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 09/10] watchdog: orion: Use BIT() Ezequiel Garcia
2013-07-15 23:32 ` [PATCH 10/10] ARM: kirkwood: Fix the device-tree watchdog's node reg property Ezequiel Garcia
2013-07-16 6:59 ` Andrew Lunn [this message]
2013-07-16 7:20 ` [PATCH 00/10] Orion Watchdog fixes Thomas Petazzoni
2013-07-16 7:31 ` Andrew Lunn
2013-07-16 7:48 ` Sebastian Hesselbarth
2013-07-16 12:17 ` Ezequiel Garcia
2013-07-16 12:14 ` Ezequiel Garcia
2013-07-16 13:44 ` Jason Cooper
2013-07-16 14:04 ` Ezequiel Garcia
2013-07-16 14:29 ` Jason Cooper
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=20130716065952.GA25043@lunn.ch \
--to=andrew@lunn.ch \
--cc=alior@marvell.com \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=maen@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wim@iguana.be \
/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).