[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b373579-7a86-6883-2624-12a5408bb49b@gmail.com>
Date: Thu, 25 Jan 2018 16:46:06 -0800
From: Frank Rowand <frowand.list@...il.com>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Wolfram Sang <wsa+renesas@...g-engineering.com>,
Steven Rostedt <rostedt@...dmis.org>,
devicetree@...r.kernel.org,
Tyrel Datwyler <tyreld@...ux.vnet.ibm.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-renesas-soc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 0/1] of: easier debugging for node life cycle
issues
On 01/25/18 15:14, Wolfram Sang wrote:
>
>> This means that ftrace can not be used for the of_node_get(),
>> of_node_put(), and of_node_release() debug info, because
>> these functions are called before early_initcall().
>
> For the record: You can still unbind/bind devices. This is how I
> debugged an issue.
I wasn't implying that the data wasn't usable for any use case.
The point is that using ftrace means there are use cases for the
debug information where the information will not be available.
Powered by blists - more mailing lists