[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190605184941.GU4797@dell>
Date: Wed, 5 Jun 2019 19:49:41 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Johan Hovold <johan@...nel.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, 05 Jun 2019, 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?
>
> Regarding this patch, however, I don't care much. I'll let the driver
> maintainers decide.
I've downgraded this to dev_dbg() in v2.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Powered by blists - more mailing lists