[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3526488-6706-22d4-1d50-6c595f6f5d3f@arm.com>
Date: Wed, 17 Jan 2018 10:43:19 +0000
From: Marc Zyngier <marc.zyngier@....com>
To: "Yang, Shunyong" <shunyong.yang@...-semitech.com>,
"tglx@...utronix.de" <tglx@...utronix.de>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Zheng, Joey" <yu.zheng@...-semitech.com>
Subject: Re: [PATCH] irqdomain: provide useful debugging information for irq
domain
On 17/01/18 10:20, Yang, Shunyong wrote:
> Hi, Thomas and Marc,
>
> On Wed, 2018-01-17 at 11:01 +0100, Thomas Gleixner wrote:
>> On Wed, 17 Jan 2018, Yang, Shunyong wrote:
>>>
>>> On Wed, 2018-01-17 at 10:33 +0100, Thomas Gleixner wrote:
>>>>
>>>> And how is that different from:
>>>>
>>>>>
>>>>>
>>>>> The nodes under debugfs irq/irqs describes information of every
>>>>> single
>>>>> irq.
>>>> Not at all. It contains the complete hierarchical information of
>>>> each
>>>> virq.
>>>>
>>> I think irq_domain_mapping can provide some high-level information
>>> in a
>>> summary style.
>>> For example, we can check all the IRQs connect to a specific irq
>>> chip
>>> or irq domain.
>> You can retrieve the same information from the irq/irqs files. All it
>> takes
>> is a shell script.
>>
>> Aside of that with hierarchical irq domains the old debug output is
>> just
>> useless.
>>
> Umm...Agree. Need I post a patch to remove it?
I'm on it.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists