diff options
| author | Deepak Saxena <[email protected]> | 2006-12-04 15:04:46 -0800 |
|---|---|---|
| committer | Jeff Garzik <[email protected]> | 2006-12-04 18:36:02 -0500 |
| commit | 33fee56ae846cdee67d2ab6d14c3baa879dfc794 (patch) | |
| tree | 96995a7c5971069168cbcd9bd18f5269dc72737d /include/linux | |
| parent | 2ad657c88d8b3c1f97c1b8cc474b6307ba7f8509 (diff) | |
[PATCH] Update smc91x driver with ARM Versatile board info
We need to specify a Versatile-specific SMC_IRQ_FLAGS value or the new
generic IRQ layer will complain thusly:
No IRQF_TRIGGER set_type function for IRQ 25 (<NULL>)
Signed-off-by: Deepak Saxena <[email protected]>
Cc: Jeff Garzik <[email protected]>
Cc: Russell King <[email protected]>
Cc: Nicolas Pitre <[email protected]>
On Fri, 20 Oct 2006 22:50:40 +0100
Russell King <[email protected]> wrote:
> On Fri, Oct 20, 2006 at 02:42:04PM -0700, [email protected] wrote:
> > We need to specify a Versatile-specific SMC_IRQ_FLAGS value or the new
> > generic IRQ layer will complain thusly:
>
> I don't think I heard anything back from my previous suggestion that
> the IRQ flags are passed through the platform device IRQ resource.
>
> Doing so would avoid adding yet another platform specific block into
> the file.
>
> BTW, Integrator platforms will also suffer from this, which will add
> another ifdef to this header.
>
> Let's do it right and arrange to pass these flags from the platform
> code. It's not like they're in a critical path.
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Jeff Garzik <[email protected]>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions