Date: Thu, 15 May 2003 09:03:50 -0700
From: Matt Porter <mporter@kernel.crashing.org>
To: Linux Kernel List <linux-kernel@vger.kernel.org>,
       Patrick Mochel <mochel@osdl.org>
Subject: Re: [PATCH] IRQ and resource for platform_device
Message-ID: <20030515090350.A7685@home.com>
References: <20030515145920.B31491@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: <20030515145920.B31491@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, May 15, 2003 at 02:59:20PM +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 787
Lines: 22

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.

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/