From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ezequiel Garcia Subject: Re: [PATCH v4 08/18] watchdog: orion: Make RSTOUT register a separate resource Date: Sun, 26 Jan 2014 10:18:56 -0300 Message-ID: <20140126131855.GB14713@localhost> References: <1390431915-5115-1-git-send-email-ezequiel.garcia@free-electrons.com> <1390431915-5115-9-git-send-email-ezequiel.garcia@free-electrons.com> <20140126091753.2910a39f@skate> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <20140126091753.2910a39f@skate> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Thomas Petazzoni Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Wim Van Sebroeck , Jason Gunthorpe , Sebastian Hesselbarth , Arnd Bergmann , Daniel Lezcano , Fabio Estevam , Andrew Lunn , Gregory Clement , Tawfik Bayouk , Lior Amsalem , Guenter Roeck , Jason Cooper List-Id: devicetree@vger.kernel.org On Sun, Jan 26, 2014 at 09:17:53AM +0100, Thomas Petazzoni wrote: [..] > > +/* > > + * The original devicetree binding for this driver specified only > > + * one memory resource, so in order to keep DT backwards compatibi= lity > > + * we try to fallback to a hardcoded register address, if the reso= urce > > + * is missing from the devicetree. > > + */ > > +static void __iomem *try_rstout_ioremap(struct platform_device *pd= ev, > > + phys_addr_t internal_regs) >=20 > Why is it called "try" ? It actually does the mapping. So I would > prefer the function to be named: >=20 > orion_wdt_ioremap_rstout() >=20 Ah, yes. This is a left over from the previous attempt. --=20 Ezequiel Garc=C3=ADa, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" i= n the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html