From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Walmsley Subject: Re: [PATCHv2 0/9] omap hwspinlock dt support Date: Mon, 30 Sep 2013 03:12:36 +0000 (UTC) Message-ID: References: <5245A8CA.4020805@ti.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: <5245A8CA.4020805-l0cyMroinI0@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Suman Anna Cc: Ohad Ben-Cohen , Benoit Cousson , Tony Lindgren , Kumar Gala , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org Hi On Fri, 27 Sep 2013, Suman Anna wrote: > Paul, > The hwmod data patches needs to be merged only after the respective DT > node patches are merged, without which the hwmod entry will not have a > base address while enabling and idling (using sysc) the hwmod during > hwmod initialization. Hmm, ideally there shouldn't be a merge dependency here. Could you please send a patch to the hwmod core that logs a warning and skips the operation in these circumstances? Or maybe just skips the registration of the device? - Paul -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html