From mboxrd@z Thu Jan 1 00:00:00 1970 From: Santosh Shilimkar Subject: Re: [RFC/NOT FOR MERGING 2/3] serial: omap: remove hwmod dependency Date: Sat, 16 Feb 2013 11:18:36 +0530 Message-ID: <511F1DB4.8030400@ti.com> References: <20130214171253.GC7144@atomide.com> <20130214175650.GA25891@arwen.pp.htv.fi> <20130214181217.GA11806@atomide.com> <20130214192719.GB26679@arwen.pp.htv.fi> <20130214193911.GD11806@atomide.com> <20130215101610.GR17852@n2100.arm.linux.org.uk> <511E3797.2070802@ti.com> <20130215132726.GT17852@n2100.arm.linux.org.uk> <511E38C3.7080404@ti.com> <20130215163031.GA5724@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from arroyo.ext.ti.com ([192.94.94.40]:44658 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750753Ab3BPFr0 (ORCPT ); Sat, 16 Feb 2013 00:47:26 -0500 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Nicolas Pitre Cc: Tony Lindgren , Paul Walmsley , Linux OMAP Mailing List , Russell King - ARM Linux , Linux ARM Kernel Mailing List , Felipe Balbi On Saturday 16 February 2013 11:06 AM, Nicolas Pitre wrote: > On Fri, 15 Feb 2013, Tony Lindgren wrote: > >> * Santosh Shilimkar [130215 05:34]: >>> On Friday 15 February 2013 06:57 PM, Russell King - ARM Linux wrote: >>>> On Fri, Feb 15, 2013 at 06:56:47PM +0530, Santosh Shilimkar wrote: >>>>> Whats your view on use of arch_ioremap_caller() hook ? This can allow >>>>> us to avoid the dual ioremap() issue discussed here if the hook >>>>> maintains the list of mapped ios. >>>>> >>>>> I was even thinking of having such intelligence within the core >>>>> ioremap code but thought that might be too invasive. >>>> >>>> Why do you even need it? There's no problem with ioremapping the same >>>> space multiple times (you end up with multiple mappings but that >>>> shouldn't be a problem, except for the additional space used.) >>>> >>> It just waste of iospace and Tony insisted to have just single ioremap() >>> hence all this discussion >> >> The main goal is to avoid duplicating data both in hwmod and DT. >> That's pretty much solved as we can have the driver probe populate >> the common data for hwmod from DT as Santosh has already demonstrated. >> >> Then we also want the driver specific idle and reset code to be done >> in the drivers rather than in hwmod and glue it together with hwmod >> using runtime PM. The biggest issue there is how do we reset and idle >> some piece of hardware for PM purposes when there's no driver loaded. >> >> For the duplicate ioremapping, I don't think there's any need to >> do it if we get things right. > > Note that if the ioremap matches a static map area there is no cost to > ioremap it multiple times. > > Thats true though now on OMAP we removed most of the static mappings. The main issue is waste of IO space because, we end up mapping same area two times for all the OMAP drivers. This can be optimized with a arch ioremap caller hook but as discussed here, its nice to have rather than something important. Regards, Santosh From mboxrd@z Thu Jan 1 00:00:00 1970 From: santosh.shilimkar@ti.com (Santosh Shilimkar) Date: Sat, 16 Feb 2013 11:18:36 +0530 Subject: [RFC/NOT FOR MERGING 2/3] serial: omap: remove hwmod dependency In-Reply-To: References: <20130214171253.GC7144@atomide.com> <20130214175650.GA25891@arwen.pp.htv.fi> <20130214181217.GA11806@atomide.com> <20130214192719.GB26679@arwen.pp.htv.fi> <20130214193911.GD11806@atomide.com> <20130215101610.GR17852@n2100.arm.linux.org.uk> <511E3797.2070802@ti.com> <20130215132726.GT17852@n2100.arm.linux.org.uk> <511E38C3.7080404@ti.com> <20130215163031.GA5724@atomide.com> Message-ID: <511F1DB4.8030400@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Saturday 16 February 2013 11:06 AM, Nicolas Pitre wrote: > On Fri, 15 Feb 2013, Tony Lindgren wrote: > >> * Santosh Shilimkar [130215 05:34]: >>> On Friday 15 February 2013 06:57 PM, Russell King - ARM Linux wrote: >>>> On Fri, Feb 15, 2013 at 06:56:47PM +0530, Santosh Shilimkar wrote: >>>>> Whats your view on use of arch_ioremap_caller() hook ? This can allow >>>>> us to avoid the dual ioremap() issue discussed here if the hook >>>>> maintains the list of mapped ios. >>>>> >>>>> I was even thinking of having such intelligence within the core >>>>> ioremap code but thought that might be too invasive. >>>> >>>> Why do you even need it? There's no problem with ioremapping the same >>>> space multiple times (you end up with multiple mappings but that >>>> shouldn't be a problem, except for the additional space used.) >>>> >>> It just waste of iospace and Tony insisted to have just single ioremap() >>> hence all this discussion >> >> The main goal is to avoid duplicating data both in hwmod and DT. >> That's pretty much solved as we can have the driver probe populate >> the common data for hwmod from DT as Santosh has already demonstrated. >> >> Then we also want the driver specific idle and reset code to be done >> in the drivers rather than in hwmod and glue it together with hwmod >> using runtime PM. The biggest issue there is how do we reset and idle >> some piece of hardware for PM purposes when there's no driver loaded. >> >> For the duplicate ioremapping, I don't think there's any need to >> do it if we get things right. > > Note that if the ioremap matches a static map area there is no cost to > ioremap it multiple times. > > Thats true though now on OMAP we removed most of the static mappings. The main issue is waste of IO space because, we end up mapping same area two times for all the OMAP drivers. This can be optimized with a arch ioremap caller hook but as discussed here, its nice to have rather than something important. Regards, Santosh