From: Thomas Gleixner <tglx@linutronix.de>
To: Marc Zyngier <maz@kernel.org>
Cc: Yash Shah <yash.shah@sifive.com>,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
robh+dt@kernel.org, mark.rutland@arm.com, palmer@dabbelt.com,
"Paul Walmsley ( Sifive)" <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, jason@lakedaemon.net, bmeng.cn@gmail.com,
atish.patra@wdc.com, Sagar Kadam <sagar.kadam@sifive.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Sachin Ghadi <sachin.ghadi@sifive.com>
Subject: Re: [PATCH v2 1/5] genirq: introduce irq_domain_translate_onecell
Date: Wed, 20 Nov 2019 11:48:28 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1911201147440.6731@nanos.tec.linutronix.de> (raw)
In-Reply-To: <31ed00455bd8374b26ea6b649c14e288@www.loen.fr>
On Wed, 20 Nov 2019, Marc Zyngier wrote:
> On 2019-11-20 09:34, Thomas Gleixner wrote:
> > On Wed, 20 Nov 2019, Yash Shah wrote:
> >
> > > Add a new function irq_domain_translate_onecell() that is to be used as
> > > the translate function in struct irq_domain_ops for the v2 IRQ API.
> >
> > What is the V2 IRQ API?
>
> I believe that's a reference to a rather misleading comment in irqdomain.h:
>
> #ifdef CONFIG_IRQ_DOMAIN_HIERARCHY
> /* extended V2 interfaces to support hierarchy irq_domains */
>
> which we could drop, as everything refers to hierarchical domain
> support.
Yes, which reminds me that we also need to update the horribly stale
documentation of all this mess.
Thanks,
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Marc Zyngier <maz@kernel.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
aou@eecs.berkeley.edu, jason@lakedaemon.net, atish.patra@wdc.com,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
bgolaszewski@baylibre.com, Yash Shah <yash.shah@sifive.com>,
robh+dt@kernel.org, palmer@dabbelt.com,
Sagar Kadam <sagar.kadam@sifive.com>,
linux-gpio@vger.kernel.org,
"Paul Walmsley \( Sifive\)" <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, bmeng.cn@gmail.com,
Sachin Ghadi <sachin.ghadi@sifive.com>
Subject: Re: [PATCH v2 1/5] genirq: introduce irq_domain_translate_onecell
Date: Wed, 20 Nov 2019 11:48:28 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1911201147440.6731@nanos.tec.linutronix.de> (raw)
In-Reply-To: <31ed00455bd8374b26ea6b649c14e288@www.loen.fr>
On Wed, 20 Nov 2019, Marc Zyngier wrote:
> On 2019-11-20 09:34, Thomas Gleixner wrote:
> > On Wed, 20 Nov 2019, Yash Shah wrote:
> >
> > > Add a new function irq_domain_translate_onecell() that is to be used as
> > > the translate function in struct irq_domain_ops for the v2 IRQ API.
> >
> > What is the V2 IRQ API?
>
> I believe that's a reference to a rather misleading comment in irqdomain.h:
>
> #ifdef CONFIG_IRQ_DOMAIN_HIERARCHY
> /* extended V2 interfaces to support hierarchy irq_domains */
>
> which we could drop, as everything refers to hierarchical domain
> support.
Yes, which reminds me that we also need to update the horribly stale
documentation of all this mess.
Thanks,
tglx
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-11-20 10:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 6:59 [PATCH v2 0/5] GPIO & Hierarchy IRQ support for HiFive Unleashed Yash Shah
2019-11-20 6:59 ` Yash Shah
2019-11-20 6:59 ` [PATCH v2 1/5] genirq: introduce irq_domain_translate_onecell Yash Shah
2019-11-20 6:59 ` Yash Shah
2019-11-20 9:34 ` Thomas Gleixner
2019-11-20 9:34 ` Thomas Gleixner
2019-11-20 10:24 ` Marc Zyngier
2019-11-20 10:24 ` Marc Zyngier
2019-11-20 10:48 ` Thomas Gleixner [this message]
2019-11-20 10:48 ` Thomas Gleixner
2019-11-20 10:38 ` Marc Zyngier
2019-11-20 10:38 ` Marc Zyngier
2019-11-21 8:35 ` Yash Shah
2019-11-21 8:35 ` Yash Shah
2019-11-21 8:55 ` Yash Shah
2019-11-21 8:55 ` Yash Shah
2019-11-21 9:20 ` Marc Zyngier
2019-11-21 9:20 ` Marc Zyngier
2019-11-20 6:59 ` [PATCH v2 2/5] irqchip: sifive: Support hierarchy irq domain Yash Shah
2019-11-20 6:59 ` Yash Shah
2019-11-22 10:17 ` Marc Zyngier
2019-11-22 10:17 ` Marc Zyngier
2019-11-20 6:59 ` [PATCH v2 3/5] gpio: sifive: Add DT documentation for SiFive GPIO Yash Shah
2019-11-20 6:59 ` Yash Shah
2019-11-20 6:59 ` [PATCH v2 4/5] gpio: sifive: Add GPIO driver for SiFive SoCs Yash Shah
2019-11-20 6:59 ` Yash Shah
2019-11-20 10:01 ` Bartosz Golaszewski
2019-11-20 10:01 ` Bartosz Golaszewski
2019-11-21 8:32 ` Yash Shah
2019-11-21 8:32 ` Yash Shah
2019-11-20 6:59 ` [PATCH v2 5/5] riscv: dts: Add DT support for SiFive FU540 GPIO driver Yash Shah
2019-11-20 6:59 ` Yash Shah
2019-11-20 9:14 ` Andreas Schwab
2019-11-20 9:14 ` Andreas Schwab
2019-11-21 8:26 ` Yash Shah
2019-11-21 8:26 ` Yash Shah
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=alpine.DEB.2.21.1911201147440.6731@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=bgolaszewski@baylibre.com \
--cc=bmeng.cn@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.com \
--cc=sagar.kadam@sifive.com \
--cc=yash.shah@sifive.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 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.