From: Matt Porter <mporter@kernel.crashing.org>
To: rmk@arm.linux.org.uk,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: [PATCH] IRQ and resource for platform_device
Date: Thu, 15 May 2003 10:35:13 -0700 [thread overview]
Message-ID: <20030515103513.B7685@home.com> (raw)
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
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
next prev parent reply other threads:[~2003-05-15 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 13:59 [PATCH] IRQ and resource for platform_device Russell King
2003-05-15 16:03 ` Matt Porter
2003-05-15 16:30 ` Russell King
2003-05-15 17:35 ` Matt Porter [this message]
2003-05-15 18:13 ` Russell King
2003-05-15 18:32 ` Matt Porter
2003-05-15 19:54 ` Patrick Mochel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030515103513.B7685@home.com \
--to=mporter@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.