From: Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> To: Quan Nguyen <qnguyen-qTEPVZfXA3Y@public.gmane.org>, Marc Zyngier <marc.zyngier-5wv7dgnIgG8@public.gmane.org> Cc: "linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>, Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>, Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>, Y Vo <yvo-qTEPVZfXA3Y@public.gmane.org>, Phong Vo <pvo-qTEPVZfXA3Y@public.gmane.org>, Loc Ho <lho-qTEPVZfXA3Y@public.gmane.org>, Feng Kan <fkan-qTEPVZfXA3Y@public.gmane.org>, Duc Dang <dhdang-qTEPVZfXA3Y@public.gmane.org>, patches <patches-qTEPVZfXA3Y@public.gmane.org> Subject: Re: [PATCH v5 1/3] gpio: xgene: Enable X-Gene standby GPIO as interrupt controller Date: Wed, 10 Feb 2016 11:58:46 +0100 [thread overview] Message-ID: <CACRpkdZXFVgtQfMM_r+xxceiAuiUDsxH-XGBOpEA9Am0BF+gRQ@mail.gmail.com> (raw) In-Reply-To: <1454041735-8434-2-git-send-email-qnguyen-qTEPVZfXA3Y@public.gmane.org> On Fri, Jan 29, 2016 at 5:28 AM, Quan Nguyen <qnguyen-qTEPVZfXA3Y@public.gmane.org> wrote: > Enable X-Gene standby GPIO controller as interrupt controller to provide > its own resources. This avoids ambiguity where GIC interrupt resource is > use as X-Gene standby GPIO interrupt resource in user driver. > > Signed-off-by: Y Vo <yvo-qTEPVZfXA3Y@public.gmane.org> > Signed-off-by: Quan Nguyen <qnguyen-qTEPVZfXA3Y@public.gmane.org> I want Marc's ACK on this before I merge it. But it is looking way more acceptable than earlier incarnations! :) > + /* Propagate IRQ type setting to parent */ > + if (type & IRQ_TYPE_EDGE_BOTH) > + return irq_chip_set_type_parent(d, IRQ_TYPE_EDGE_RISING); > + else > + return irq_chip_set_type_parent(d, IRQ_TYPE_LEVEL_HIGH); This makes it look much more solid, nice. > +static void xgene_gpio_sb_irq_shutdown(struct irq_data *d) > +{ > + struct xgene_gpio_sb *priv = irq_data_get_irq_chip_data(d); > + > + gpiochip_unlock_as_irq(&priv->gc, HWIRQ_TO_GPIO(priv, d->hwirq)); Oh really. Well. > + if (is_of_node(domain->parent->fwnode)) { > + parent_fwspec.fwnode = domain->parent->fwnode; > + parent_fwspec.param_count = 3; > + parent_fwspec.param[0] = 0;/* SPI */ > + /* Skip SGIs and PPIs*/ > + parent_fwspec.param[1] = hwirq + priv->parent_irq_base - 32; > + parent_fwspec.param[2] = fwspec->param[1]; > + } else if (is_fwnode_irqchip(domain->parent->fwnode)) { > + parent_fwspec.fwnode = domain->parent->fwnode; > + parent_fwspec.param_count = 2; > + parent_fwspec.param[0] = hwirq + priv->parent_irq_base; > + parent_fwspec.param[1] = fwspec->param[1]; > + } else > + return -EINVAL; This kind of stuff hardcodes knowledge of the GIC into this controller, like that the SGI+PPI occupy the first 32 hwIRQs. But maybe there is no better way to do it? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v5 1/3] gpio: xgene: Enable X-Gene standby GPIO as interrupt controller Date: Wed, 10 Feb 2016 11:58:46 +0100 [thread overview] Message-ID: <CACRpkdZXFVgtQfMM_r+xxceiAuiUDsxH-XGBOpEA9Am0BF+gRQ@mail.gmail.com> (raw) In-Reply-To: <1454041735-8434-2-git-send-email-qnguyen@apm.com> On Fri, Jan 29, 2016 at 5:28 AM, Quan Nguyen <qnguyen@apm.com> wrote: > Enable X-Gene standby GPIO controller as interrupt controller to provide > its own resources. This avoids ambiguity where GIC interrupt resource is > use as X-Gene standby GPIO interrupt resource in user driver. > > Signed-off-by: Y Vo <yvo@apm.com> > Signed-off-by: Quan Nguyen <qnguyen@apm.com> I want Marc's ACK on this before I merge it. But it is looking way more acceptable than earlier incarnations! :) > + /* Propagate IRQ type setting to parent */ > + if (type & IRQ_TYPE_EDGE_BOTH) > + return irq_chip_set_type_parent(d, IRQ_TYPE_EDGE_RISING); > + else > + return irq_chip_set_type_parent(d, IRQ_TYPE_LEVEL_HIGH); This makes it look much more solid, nice. > +static void xgene_gpio_sb_irq_shutdown(struct irq_data *d) > +{ > + struct xgene_gpio_sb *priv = irq_data_get_irq_chip_data(d); > + > + gpiochip_unlock_as_irq(&priv->gc, HWIRQ_TO_GPIO(priv, d->hwirq)); Oh really. Well. > + if (is_of_node(domain->parent->fwnode)) { > + parent_fwspec.fwnode = domain->parent->fwnode; > + parent_fwspec.param_count = 3; > + parent_fwspec.param[0] = 0;/* SPI */ > + /* Skip SGIs and PPIs*/ > + parent_fwspec.param[1] = hwirq + priv->parent_irq_base - 32; > + parent_fwspec.param[2] = fwspec->param[1]; > + } else if (is_fwnode_irqchip(domain->parent->fwnode)) { > + parent_fwspec.fwnode = domain->parent->fwnode; > + parent_fwspec.param_count = 2; > + parent_fwspec.param[0] = hwirq + priv->parent_irq_base; > + parent_fwspec.param[1] = fwspec->param[1]; > + } else > + return -EINVAL; This kind of stuff hardcodes knowledge of the GIC into this controller, like that the SGI+PPI occupy the first 32 hwIRQs. But maybe there is no better way to do it? Yours, Linus Walleij
next prev parent reply other threads:[~2016-02-10 10:58 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-01-29 4:28 [PATCH v5 0/3] Enable X-Gene standby GPIO as interrupt controller Quan Nguyen 2016-01-29 4:28 ` Quan Nguyen 2016-01-29 4:28 ` [PATCH v5 1/3] gpio: xgene: " Quan Nguyen 2016-01-29 4:28 ` Quan Nguyen [not found] ` <1454041735-8434-2-git-send-email-qnguyen-qTEPVZfXA3Y@public.gmane.org> 2016-02-10 10:58 ` Linus Walleij [this message] 2016-02-10 10:58 ` Linus Walleij 2016-02-10 15:09 ` Marc Zyngier 2016-02-10 15:09 ` Marc Zyngier [not found] ` <56BB52B8.4040501-5wv7dgnIgG8@public.gmane.org> 2016-02-11 16:35 ` Quan Nguyen 2016-02-11 16:35 ` Quan Nguyen 2016-02-15 23:26 ` Linus Walleij 2016-02-15 23:26 ` Linus Walleij 2016-01-29 4:28 ` [PATCH v5 2/3] Documentation: gpio: Update description for X-Gene standby GPIO controller DTS binding Quan Nguyen 2016-01-29 4:28 ` Quan Nguyen [not found] ` <1454041735-8434-3-git-send-email-qnguyen-qTEPVZfXA3Y@public.gmane.org> 2016-02-01 15:35 ` Rob Herring 2016-02-01 15:35 ` Rob Herring 2016-02-02 1:46 ` Quan Nguyen 2016-02-02 1:46 ` Quan Nguyen 2016-02-12 14:36 ` Rob Herring 2016-02-12 14:36 ` Rob Herring 2016-02-13 3:21 ` Quan Nguyen 2016-02-13 3:21 ` Quan Nguyen 2016-01-29 4:28 ` [PATCH v5 3/3] arm64: dts: Update X-Gene standby GPIO controller DTS entries Quan Nguyen 2016-01-29 4:28 ` Quan Nguyen
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=CACRpkdZXFVgtQfMM_r+xxceiAuiUDsxH-XGBOpEA9Am0BF+gRQ@mail.gmail.com \ --to=linus.walleij-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=dhdang-qTEPVZfXA3Y@public.gmane.org \ --cc=fkan-qTEPVZfXA3Y@public.gmane.org \ --cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \ --cc=lho-qTEPVZfXA3Y@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=marc.zyngier-5wv7dgnIgG8@public.gmane.org \ --cc=patches-qTEPVZfXA3Y@public.gmane.org \ --cc=pvo-qTEPVZfXA3Y@public.gmane.org \ --cc=qnguyen-qTEPVZfXA3Y@public.gmane.org \ --cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \ --cc=yvo-qTEPVZfXA3Y@public.gmane.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: linkBe 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.