Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264127AbTEORWb (ORCPT ); Thu, 15 May 2003 13:22:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264130AbTEORWb (ORCPT ); Thu, 15 May 2003 13:22:31 -0400 Received: from fed1mtao08.cox.net ([68.6.19.123]:28293 "EHLO fed1mtao08.cox.net") by vger.kernel.org with ESMTP id S264127AbTEORW3 (ORCPT ); Thu, 15 May 2003 13:22:29 -0400 Date: Thu, 15 May 2003 10:35:13 -0700 From: Matt Porter To: rmk@arm.linux.org.uk, Linux Kernel List , Patrick Mochel Subject: Re: [PATCH] IRQ and resource for platform_device Message-ID: <20030515103513.B7685@home.com> References: <20030515145920.B31491@flint.arm.linux.org.uk> <20030515090350.A7685@home.com> <20030515173052.C31491@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030515173052.C31491@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, May 15, 2003 at 05:30:52PM +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1378 Lines: 37 On Thu, May 15, 2003 at 05:30:52PM +0100, Russell King wrote: > On Thu, May 15, 2003 at 09:03:50AM -0700, Matt Porter wrote: > > On Thu, May 15, 2003 at 02:59:20PM +0100, Russell King wrote: > > > The location and interrupt of some platform devices are only known by > > > platform specific code. In order to avoid putting platform specific > > > parameters into drivers, place resource and irq members into struct > > > platform_device. > > > > > > Discussion point: is one resource and one irq enough? > > > > No. > > > > We have the same need for PPC SoC and system controller on-chip > > devices. Some devices have multiple interrupts and/or resources. > > Is there a sane limit on the number of interrupts and resources for one > device? As of today, I know of a device that has 5 interrupts and another with 2 interrupts. I believe two resources is the most I've seen so far on a "dumb" on-chip device. I think having an array of irqs and resources of max count 8 should do it for now. No matter what we choose, the hardware designers will screw it up eventually. Regards, -- Matt Porter mporter@kernel.crashing.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/