From: Kumar Gala <galak@kernel.crashing.org>
To: Andy Fleming <afleming@freescale.com>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] Slight refactor of interrupt mapping for FSL parts
Date: Mon, 16 Oct 2006 16:54:29 -0500 [thread overview]
Message-ID: <87415DCF-94DA-4D33-8255-3D6E2E72C06E@kernel.crashing.org> (raw)
In-Reply-To: <C6870308-059D-40F8-8567-7A11AFAD2AE2@kernel.crashing.org>
On Oct 16, 2006, at 4:37 PM, Kumar Gala wrote:
>
> On Oct 16, 2006, at 3:57 PM, Andy Fleming wrote:
>
>>
>> * Cleaned up interrupt mapping a little by adding a helper
>> function which parses the irq out of the device-tree, and puts
>> it into a resource.
>> * Changed the PHY Layer to use NO_IRQ instead of -1 for PHY_POLL.
>> This means that polling will always be used if mapping the
>> interrupt fails for any reason.
>
> You forgot to fixup the arch/ppc users of this.
>
>
>> ---
>> arch/powerpc/sysdev/fsl_soc.c | 33 +++++++++++++++
>> +-----------------
>> include/linux/phy.h | 2 +-
>> 2 files changed, 17 insertions(+), 18 deletions(-)
>>
>> diff --git a/arch/powerpc/sysdev/fsl_soc.c b/arch/powerpc/sysdev/
>> fsl_soc.c
>> index dbe92ae..aa24b51 100644
>> --- a/arch/powerpc/sysdev/fsl_soc.c
>> +++ b/arch/powerpc/sysdev/fsl_soc.c
>> @@ -146,7 +146,7 @@ static int __init gfar_mdio_of_init(void
>> }
>>
>> for (k = 0; k < 32; k++)
>> - mdio_data.irq[k] = -1;
>> + mdio_data.irq[k] = NO_IRQ;
>>
>> while ((child = of_get_next_child(np, child)) != NULL) {
>> int irq = irq_of_parse_and_map(child, 0);
>> @@ -177,6 +177,13 @@ static const char *gfar_tx_intr = "tx";
>> static const char *gfar_rx_intr = "rx";
>> static const char *gfar_err_intr = "error";
>>
>> +
>> +void of_irq_to_resource(struct device_node *dev, int index, struct
>> resource *r)
>> +{
>> + r->start = r->end = irq_of_parse_and_map(dev, index);
>> + r->flags = IORESOURCE_IRQ;
>> +}
>
> Why don't you stick this in prom_parse.c (and add a prototype to
> prom.h)
Actually, just implement it in the header.
- k
next prev parent reply other threads:[~2006-10-16 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 20:57 [PATCH] Slight refactor of interrupt mapping for FSL parts Andy Fleming
2006-10-16 21:37 ` Kumar Gala
2006-10-16 21:51 ` Joakim Tjernlund
2006-10-18 13:50 ` Vitaly Bordug
2006-10-19 19:14 ` Andy Fleming
2006-10-19 22:40 ` Joakim Tjernlund
2006-10-20 0:54 ` Andy Fleming
2006-10-16 21:54 ` Kumar Gala [this message]
2006-10-16 22:58 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-10-17 6:27 Andy Fleming
2006-10-17 15:50 ` Kumar Gala
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=87415DCF-94DA-4D33-8255-3D6E2E72C06E@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=afleming@freescale.com \
--cc=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).