On 10/29/2014 04:56 PM, Andrew Bresticker wrote:
On Wed, Oct 29, 2014 at 4:01 AM, Qais Yousef <qais.yousef@xxxxxxxxxx> wrote:
On 10/29/2014 12:12 AM, Andrew Bresticker wrote:
+- mti,available-cpu-vectors : Specifies the list of CPU interrupt vectors
+ to which the GIC may route interrupts. May contain up to 6 entries,
one
+ for each of the CPU's hardware interrupt vectors. Valid values are 2 -
7.
+ This property is ignored if the CPU is started in EIC mode.
+
Wouldn't it be better to have this in the reversed sense ie:
mti,nonavailable-cpu-vectors? I think the assumption that by default they're
all available unless something else is connected to them which is unlikely
in most cases. It can be made optional property then.
I don't have a strong opinion about it though.
Actually, I think I like the reversed sense as well. Perhaps
"mti,reserved-cpu-vectors"?
Yep that's a better wording for sure :)
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
