From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Subject: Re: [PATCH 0/4] ARM: shmobile: R-Mobile: Add SYSC restart handler Date: Thu, 4 Dec 2014 21:18:23 +0900 Message-ID: <20141204121823.GA21778@verge.net.au> References: <1417616227-6715-1-git-send-email-geert+renesas@glider.be> <20141204073409.GG25806@verge.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-sh-owner@vger.kernel.org To: Geert Uytterhoeven Cc: Geert Uytterhoeven , Magnus Damm , Arnd Bergmann , Linux-sh list , Linux PM list , "linux-arm-kernel@lists.infradead.org" List-Id: linux-pm@vger.kernel.org On Thu, Dec 04, 2014 at 10:39:59AM +0100, Geert Uytterhoeven wrote: > Hi Simon, > > On Thu, Dec 4, 2014 at 8:34 AM, Simon Horman wrote: > > On Wed, Dec 03, 2014 at 03:17:03PM +0100, Geert Uytterhoeven wrote: > >> This patch series extends the PM domain platform driver for the R-Mobile > >> System Controller (SYSC) to register a restart handler, and removes the > >> restart handler hacks on DT-based R-Mobile A1 (r8a7740) and SH-Mobile AG5 > >> (sh73a0) platforms. > >> > >> Note that this supports DT-based platforms only. Legacy platforms keep > >> on using the restart callback in struct machine_desc. > >> > >> This was tested on r8a7740/armadillo-multiplatform, > >> sh73a0/kzm9g-reference, and sh73a0/kzm9g-multiplatform. > >> > >> Arnd: is this what you had in mind in your response to "[GIT PULL] Third > >> Round of Renesas ARM Based Soc Updates for v3.19" > >> (http://www.spinics.net/lists/arm-kernel/msg379348.html)? > >> > >> Dependencies: > >> - The first two patches depend on the series "[PATCH v6 0/7] ARM: > >> shmobile: R-Mobile: DT PM domain support", as that series adds the > >> SYSC PM domain platform driver for DT-based platforms and adds the > >> SYSC device node to r8a7740.dtsi, > > > > As I have queued up that series I believe I could also queue up > > the first two patches of this series. Is that worthwhile? > > Yes you can, if Arnd doesn't object against the driver. Thanks, I'll wait for a resolution to that discussion.