From: Gabor Juhos <juhosg@openwrt.org>
To: John Crispin <blogic@openwrt.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>,
"Rodriguez, Luis" <rodrigue@qca.qualcomm.com>,
"Giori, Kathy" <kgiori@qca.qualcomm.com>,
QCA Linux Team <qca-linux-team@qca.qualcomm.com>
Subject: Re: [PATCH 04/11] MIPS: ath79: add IRQ handling code for the QCA955X SoCs
Date: Fri, 15 Feb 2013 18:26:44 +0100 [thread overview]
Message-ID: <511E6FD4.6060802@openwrt.org> (raw)
In-Reply-To: <511E5BD9.1040407@openwrt.org>
2013.02.15. 17:01 keltezéssel, John Crispin írta:
>
>>
>> if (soc_is_ar71xx() || soc_is_ar913x())
>> ath79_misc_irq_chip.irq_mask_ack = ar71xx_misc_irq_mask;
>> - else if (soc_is_ar724x() || soc_is_ar933x() || soc_is_ar934x())
>> + else if (soc_is_ar724x() ||
>> + soc_is_ar933x() ||
>> + soc_is_ar934x() ||
>> + soc_is_qca955x())
>> ath79_misc_irq_chip.irq_ack = ar724x_misc_irq_ack;
> Hi,
>
> the list is getting long. not a blocker but might be worth thinking of a
> different way to solve the different revisions of the irq core
This code runs only once, so it is not worth the effort IMHO.
If I would introduce a table to store the revision of the IRQ core, I would have
to put a value into that for each different SoC. That means 15 entries at the
moment.
Alternatively I can introduce a global variable to store the revision, and
intialize that variable from the SoC detection code. However I would have to set
that variable individually for each SoC and that means 15 lines of code.
>> + if (status& QCA955X_EXT_INT_USB1) {
>> + /* TODO: flush DDR? */
>> + generic_handle_irq(ATH79_IP3_IRQ(0));
>> + }
>> +
>> + if (status& QCA955X_EXT_INT_USB2) {
>> + /* TODO: flsuh DDR? */
>> + generic_handle_irq(ATH79_IP3_IRQ(1));
>> + }
>
> flsuh typo
Yep, will fix it.
Thanks,
Gabor
next prev parent reply other threads:[~2013-02-15 17:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 14:38 [PATCH 00/11] MIPS: ath79: add support for the QCA955X SoCs Gabor Juhos
2013-02-15 14:38 ` [PATCH 01/11] MIPS: ath79: add early printk " Gabor Juhos
2013-02-15 14:38 ` [PATCH 02/11] MIPS: ath79: add SoC detection code " Gabor Juhos
2013-02-15 16:00 ` John Crispin
2013-02-15 16:42 ` Gabor Juhos
2013-02-15 14:38 ` [PATCH 03/11] MIPS: ath79: add clock setup " Gabor Juhos
2013-02-15 14:38 ` [PATCH 04/11] MIPS: ath79: add IRQ handling " Gabor Juhos
2013-02-15 16:01 ` John Crispin
2013-02-15 17:26 ` Gabor Juhos [this message]
2013-02-15 14:38 ` [PATCH 05/11] MIPS: ath79: add GPIO setup " Gabor Juhos
2013-02-15 14:38 ` [PATCH 06/11] MIPS: ath79: add QCA955X specific glue to ath79_device_reset_{set,clear} Gabor Juhos
2013-02-15 14:38 ` [PATCH 07/11] MIPS: ath79: register UART for the QCA955X SoCs Gabor Juhos
2013-02-15 14:38 ` [PATCH 08/11] MIPS: ath79: add WMAC registration code " Gabor Juhos
2013-02-15 16:01 ` John Crispin
2013-02-15 17:13 ` Gabor Juhos
2013-02-15 14:38 ` [PATCH 09/11] MIPS: ath79: add PCI controller " Gabor Juhos
2013-02-15 14:38 ` [PATCH 10/11] MIPS: ath79: add USB " Gabor Juhos
2013-02-15 14:38 ` [PATCH 11/11] MIPS: ath79: add support for the Qualcomm Atheros AP136-010 board Gabor Juhos
2013-02-15 16:02 ` John Crispin
2013-02-15 17:34 ` Gabor Juhos
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=511E6FD4.6060802@openwrt.org \
--to=juhosg@openwrt.org \
--cc=blogic@openwrt.org \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-mips@linux-mips.org \
--cc=qca-linux-team@qca.qualcomm.com \
--cc=ralf@linux-mips.org \
--cc=rodrigue@qca.qualcomm.com \
/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