From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753868Ab2DWGwQ (ORCPT ); Mon, 23 Apr 2012 02:52:16 -0400 Received: from mail-pz0-f51.google.com ([209.85.210.51]:51962 "EHLO mail-pz0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753780Ab2DWGwO (ORCPT ); Mon, 23 Apr 2012 02:52:14 -0400 Date: Mon, 23 Apr 2012 14:53:01 +0800 From: Shawn Guo To: Sascha Hauer Cc: Rob Lee , Amit Kucheria , kernel@pengutronix.de, linaro-dev@lists.linaro.org, patches@linaro.org, daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 1/3] ARM: imx: Add common imx cpuidle init functionality. Message-ID: <20120423065259.GR26306@S2101-09.ap.freescale.net> References: <20120417074301.GM20478@pengutronix.de> <20120417174213.GD3852@pengutronix.de> <20120419064308.GH3852@pengutronix.de> <20120420020816.GH22219@S2101-09.ap.freescale.net> <20120423051813.GM26306@S2101-09.ap.freescale.net> <20120423062739.GX3852@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120423062739.GX3852@pengutronix.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 23, 2012 at 08:27:39AM +0200, Sascha Hauer wrote: > On Mon, Apr 23, 2012 at 01:18:21PM +0800, Shawn Guo wrote: > > On Sun, Apr 22, 2012 at 11:44:39PM -0500, Rob Lee wrote: > > > >> I don't think we need a cpu_is_imx6q(), but having some i.MX6 specific > > > >> hook at device_initcall time can't be too wrong. Shawn? > > > >> > > > > Yep, it works for me. > > > > > > > Sascha, Shawn, thanks for the response. > > > > > > Since device_initcall isn't platform specific, it seems I would still > > > need a cpu_is_imx6q() function or similiar functionality from a device > > > tree call. Or do you have something else in mind that I'm not seeing? > > > > > I guess Sascha is asking for something like the following. > > > > static int __init imx_device_init(void) > > { > > imx5_device_init(); > > imx6_device_init(); > > } > > device_initcall(imx_device_init) > > > > static int __init imx6_device_init(void) > > { > > /* > > * do whatever needs to get done in device_initcall time > > */ > > } > > The problem is more how we can detect that we are actually running a > i.MX6 SoC. We could directly ask the devicetree in an initcall or we > could introduce a cpu_is_mx6() just like we have a macro for all other > i.MX SoCs. > Oops, my reply was a brain-dead one. Hmm, then it seems that we have to introduce cpu_is_mx6() which I tried hard to avoid. I do not have a preference between defining a macro and asking device tree. -- Regards, Shawn