Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752260AbbEFTMy (ORCPT ); Wed, 6 May 2015 15:12:54 -0400 Received: from mout.kundenserver.de ([212.227.17.10]:53991 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750845AbbEFTMv (ORCPT ); Wed, 6 May 2015 15:12:51 -0400 From: Arnd Bergmann To: Brian Norris Cc: linux-mtd@lists.infradead.org, Dmitry Torokhov , Anatol Pomazao , Ray Jui , Corneliu Doban , Jonathan Richardson , Scott Branden , Florian Fainelli , =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , bcm-kernel-feedback-list@broadcom.com, Dan Ehrenberg , Gregory Fong , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Kevin Cernekee Subject: Re: [PATCH v3 06/10] mtd: brcmstb_nand: add SoC-specific support Date: Wed, 06 May 2015 21:12:43 +0200 Message-ID: <7101952.uOJDgn7tgf@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1430935194-7579-7-git-send-email-computersforpeace@gmail.com> References: <1430935194-7579-1-git-send-email-computersforpeace@gmail.com> <1430935194-7579-7-git-send-email-computersforpeace@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:6mH2PGvKvTAs294rYH4sjLUuubIws83S87kh2AJQO3HotbQUxyc wemP0eduEVHWAsoWPSsCQAgPsPFxqYJNne9aglIzOafB6AziaJsGBTyQ31+FFYgqTeErrbW c84XLI9boZffFj0AvtUiA6hat0GVGj84e5+8zMWswZlNokOOUXKw2X3Q0OGMGMLVQ1lRPZI 8qfEvthXhrfqTCT6H9XtA== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1806 Lines: 47 On Wednesday 06 May 2015 10:59:50 Brian Norris wrote: > + /* > + * Some SoCs integrate this controller (e.g., its interrupt bits) in > + * interesting ways > + */ > + if (of_property_read_bool(dn, "brcm,nand-soc")) { > + struct device_node *soc_dn; > + > + soc_dn = of_parse_phandle(dn, "brcm,nand-soc", 0); > + if (!soc_dn) > + return -ENODEV; > + > + ctrl->soc = devm_brcmnand_probe_soc(dev, soc_dn); > + if (!ctrl->soc) { > + dev_err(dev, "could not probe SoC data\n"); > + of_node_put(soc_dn); > + return -ENODEV; > + } > + > + ret = devm_request_irq(dev, ctrl->irq, brcmnand_irq, 0, > + DRV_NAME, ctrl); > + > + /* Enable interrupt */ > + ctrl->soc->ctlrdy_set_enabled(ctrl->soc, true); > + > + of_node_put(soc_dn); > + } else { > + /* Use standard interrupt infrastructure */ > + ret = devm_request_irq(dev, ctrl->irq, brcmnand_ctlrdy_irq, 0, > + DRV_NAME, ctrl); > + } > It looks to me like this should be handled as a nested irqchip, so the node you look up gets used as the "interrupt-parent" instead, making the behavior of this SoC transparent to the nand driver. We recently merged nested irqdomain support as well, which might help here, or might not be needed. Arnd -- 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/