[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190612145445.GB18153@localhost>
Date: Wed, 12 Jun 2019 16:54:45 +0200
From: Johan Hovold <johan@...nel.org>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Johan Hovold <johan@...nel.org>, Lee Jones <lee.jones@...aro.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>, balbi@...nel.org,
wsa+renesas@...g-engineering.com, gregkh@...uxfoundation.org,
linus.walleij@...aro.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, david.brown@...aro.org,
alokc@...eaurora.org, kramasub@...eaurora.org,
linux-i2c@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-arm-msm@...r.kernel.org, andy.gross@...aro.org,
jlhugo@...il.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 2/8] i2c: i2c-qcom-geni: Signify successful driver probe
On Wed, Jun 05, 2019 at 04:18:12PM +0200, Wolfram Sang wrote:
>
> > To enable dynamic debugging in driver core you could use something like
> >
> > CONFIG_CMDLINE="dyndbg=\"func really_probe =p\""
> >
> > That gives you two printouts per successful probe, for example:
> >
> > bus: 'usb-serial': really_probe: probing driver edgeport_ti_1 with device ttyUSB0
> > bus: 'usb-serial': really_probe: bound device ttyUSB0 to driver edgeport_ti_1
>
> I agree that this scales much better than adding strings to every
> driver. Also, the driver core will report failed probes other than
> -ENODEV, or?
Right, errors other than -EPROBE_DEFER, -ENODEV and -ENXIO are always
logged, and the previous three would also be logged with debugging
enabled.
Johan
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists