[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb4a28cb-2005-4e9b-8b3d-4d9f4c667c8f@arm.com>
Date: Thu, 7 Sep 2017 13:47:16 +0100
From: Marc Zyngier <marc.zyngier@....com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Thomas Gleixner <tglx@...utronix.de>,
Linus Walleij <linus.walleij@...aro.org>,
linux-gpio@...r.kernel.org, Rob Herring <robh+dt@...nel.org>
Cc: Jassi Brar <jaswinder.singh@...aro.org>,
devicetree@...r.kernel.org, Jason Cooper <jason@...edaemon.net>,
Masami Hiramatsu <mhiramat@...nel.org>,
David Daney <david.daney@...ium.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/6] irqdomain: rename variables in
irq_domain_{push,pop}_irq()
On 07/09/17 12:41, Masahiro Yamada wrote:
> The meaning of "root" in irq_domain_{push,pop} is opposite to the
> documentation. Documentation/IRQ-domain.txt depicts the hierarchy
> IRQ domain as follows:
>
> CPU Vector irq_domain (root irq_domain to manage CPU vectors)
> ^
> |
> Interrupt Remapping irq_domain (manage irq_remapping entries)
> ^
> |
> IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
>
> From above, the inner-most domain (nearest to the CPU) is "root".
>
> The document also says, "When building irq_domain hierarchy, the
> irq_domain near to the device is child and the irq_domain near to
> CPU is parent." This is how irq_data->parent_data works. In
> contrast, these function use a variable "child_irq_data" for that.
The exact opposite argument could be used for the data structure. The
irq_desc is the root of the list ordered with parent_data.
Yes, this is confusing, but because we're using the same English words
to describe two different things, we're bound to make one thing more
difficult. I'm unconvinced that this change helps anything (it certainly
confuses me more than anything else).
Thanks,
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists