On 09.04.18, Tobias Regnery wrote:
> On 09.04.18, Heikki Krogerus wrote:
> > On Mon, Apr 09, 2018 at 09:55:17AM +0200, Tobias Regnery wrote:
> > > The ucsi driver defines several tracepoints, but the header file with the
> > > tracepoint definition trace.h is only conditionally built depending on
Hi Tobias,
On Mon, Apr 09, 2018 at 01:40:53PM +0200, Tobias Regnery wrote:
> You are right, building a defconfig, enable the UCSI driver and disable
> CONFIG_FTRACE indeed builds without problems. So it must be some other
> combination of config options. Attached is the randconfig which triggers
On 09.04.18, Heikki Krogerus wrote:
> On Mon, Apr 09, 2018 at 09:55:17AM +0200, Tobias Regnery wrote:
> > The ucsi driver defines several tracepoints, but the header file with the
> > tracepoint definition trace.h is only conditionally built depending on
> > CONFIG_FTRACE.
>
> You mean trace.c,
On Mon, Apr 09, 2018 at 09:55:17AM +0200, Tobias Regnery wrote:
> The ucsi driver defines several tracepoints, but the header file with the
> tracepoint definition trace.h is only conditionally built depending on
> CONFIG_FTRACE.
You mean trace.c, right? The definitions are indeed in the header,
The ucsi driver defines several tracepoints, but the header file with the
tracepoint definition trace.h is only conditionally built depending on
CONFIG_FTRACE.
This leads to the following build error with CONFIG_FTRACE=n and
CONFIG_TYPEC_UCSI=m:
ERROR: "__tracepoint_ucsi_command"