From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 08/10] ARM: OMAP5: hwmod data: Create initial OMAP5 SOC hwmod data Date: Fri, 25 Jan 2013 08:55:14 -0800 Message-ID: <20130125165513.GX22517@atomide.com> References: <1358522856-12180-1-git-send-email-santosh.shilimkar@ti.com> <1358522856-12180-9-git-send-email-santosh.shilimkar@ti.com> <20130118171500.GC15361@atomide.com> <50FCF838.6000105@ti.com> <50FD5993.5010008@ti.com> <20130121180113.GA22517@atomide.com> <50FE909B.1020001@ti.com> <20130122183942.GO15361@atomide.com> <510103F9.4080601@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:59343 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756678Ab3AYQzR (ORCPT ); Fri, 25 Jan 2013 11:55:17 -0500 Content-Disposition: inline In-Reply-To: <510103F9.4080601@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Rajendra Nayak Cc: Santosh Shilimkar , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, mturquette@linaro.org, b-cousson@ti.com, Paul Walmsley * Rajendra Nayak [130124 01:54]: > On Wednesday 23 January 2013 12:09 AM, Tony Lindgren wrote: > >It seems that we should have the iospace available in the driver > >at that point. And it should be also available to the runtime PM > >code in hwmod in the device somewhere? > > I couldn't find anything as part of the device. Definitely not the > ioremaped address. There's a device_private->driver_data which the > drivers can use to populate the ioremaped address but I am sure thats > not whats its meant for. I guess we could have runtime PM init function to pass the driver region to the low level bus code if needed. Anybody got better ideas? Regards, Tony From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Fri, 25 Jan 2013 08:55:14 -0800 Subject: [PATCH 08/10] ARM: OMAP5: hwmod data: Create initial OMAP5 SOC hwmod data In-Reply-To: <510103F9.4080601@ti.com> References: <1358522856-12180-1-git-send-email-santosh.shilimkar@ti.com> <1358522856-12180-9-git-send-email-santosh.shilimkar@ti.com> <20130118171500.GC15361@atomide.com> <50FCF838.6000105@ti.com> <50FD5993.5010008@ti.com> <20130121180113.GA22517@atomide.com> <50FE909B.1020001@ti.com> <20130122183942.GO15361@atomide.com> <510103F9.4080601@ti.com> Message-ID: <20130125165513.GX22517@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Rajendra Nayak [130124 01:54]: > On Wednesday 23 January 2013 12:09 AM, Tony Lindgren wrote: > >It seems that we should have the iospace available in the driver > >at that point. And it should be also available to the runtime PM > >code in hwmod in the device somewhere? > > I couldn't find anything as part of the device. Definitely not the > ioremaped address. There's a device_private->driver_data which the > drivers can use to populate the ioremaped address but I am sure thats > not whats its meant for. I guess we could have runtime PM init function to pass the driver region to the low level bus code if needed. Anybody got better ideas? Regards, Tony