From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurent Pinchart Date: Tue, 03 Feb 2015 13:47:44 +0000 Subject: Re: [RFC 4/5] ARM: shmobile: r8a7790: let rst module allow watchdog resets if desired Message-Id: <26850628.qusLeioCVX@avalon> List-Id: References: <1422802074-1921-5-git-send-email-wsa@the-dreams.de> In-Reply-To: <1422802074-1921-5-git-send-email-wsa@the-dreams.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-sh@vger.kernel.org On Tuesday 03 February 2015 13:12:31 Geert Uytterhoeven wrote: > Hi Wolfram, > > On Mon, Feb 2, 2015 at 12:13 PM, Wolfram Sang wrote: > >> It's slightly more complicated there, as we already have a driver for the > >> SYSC on R-Mobile (rmobile-reset), and a device node can't be bound > >> by both the syscon and the rmobile-reset driver. > > > > Is it just complicated or is it an open issue how to handle that? > > If the syscon drivers binds against the device, rmobile-reset can no > longer bind against it. One solution is to convert rmobile-reset to use > syscon, so both the rwdt and the rmobile-reset drivers would access it > through syscon. > But currently syscon provides access to the first register bank of a device > only, while the RESCNT register is part of the second bank. Shouldn't syscon be split into an API that individual drivers can implement and a default driver for syscon devices that just need to expose one register bank ? > >> Do you have a better idea? > > > > Nope. I also thought that something like syscon must be used if the > > initialization in arch-code won't work. Still, I tried first with the > > least intrusive version :) -- Regards, Laurent Pinchart