From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH 1/2] mfd: add irq domain support for max8997 interrupts Date: Fri, 9 Dec 2011 14:39:13 +0800 Message-ID: <20111209063912.GG26952@opensource.wolfsonmicro.com> References: <1323361659-11835-1-git-send-email-thomas.abraham@linaro.org> <1323361659-11835-2-git-send-email-thomas.abraham@linaro.org> <20111209044109.GB26952@opensource.wolfsonmicro.com> <20111209060249.GD26952@opensource.wolfsonmicro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from opensource.wolfsonmicro.com ([80.75.67.52]:47176 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750784Ab1LIGjT (ORCPT ); Fri, 9 Dec 2011 01:39:19 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: Thomas Abraham Cc: linux-kernel@vger.kernel.org, rpurdie@rpsys.net, rob.herring@calxeda.com, grant.likely@secretlab.ca, kgene.kim@samsung.com, myungjoo.ham@samsung.com, kyungmin.park@samsung.com, dg77.kim@samsung.com, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org On Fri, Dec 09, 2011 at 12:00:07PM +0530, Thomas Abraham wrote: > If these gpio's are connected to the host system, and host system sets > up gpio interrupt notification for these gpio lines, the linux irq > number for the gpio interrupt would belong to the irq domain of the > host interrupt controller (gic irq domain in case of exynos). > Consumers of this interrupt would use the gpio interrupt independent > of the max8997 irq domain. So irq_base can be maintained private to > the max8997 mfd driver and its sub-block drivers. How would you provide this interrupt to the device using it in a non-DT systemm without passing the irq_base into the device as platform data? From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@opensource.wolfsonmicro.com (Mark Brown) Date: Fri, 9 Dec 2011 14:39:13 +0800 Subject: [PATCH 1/2] mfd: add irq domain support for max8997 interrupts In-Reply-To: References: <1323361659-11835-1-git-send-email-thomas.abraham@linaro.org> <1323361659-11835-2-git-send-email-thomas.abraham@linaro.org> <20111209044109.GB26952@opensource.wolfsonmicro.com> <20111209060249.GD26952@opensource.wolfsonmicro.com> Message-ID: <20111209063912.GG26952@opensource.wolfsonmicro.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Dec 09, 2011 at 12:00:07PM +0530, Thomas Abraham wrote: > If these gpio's are connected to the host system, and host system sets > up gpio interrupt notification for these gpio lines, the linux irq > number for the gpio interrupt would belong to the irq domain of the > host interrupt controller (gic irq domain in case of exynos). > Consumers of this interrupt would use the gpio interrupt independent > of the max8997 irq domain. So irq_base can be maintained private to > the max8997 mfd driver and its sub-block drivers. How would you provide this interrupt to the device using it in a non-DT systemm without passing the irq_base into the device as platform data?