Re: [PATCH 2/8] i2c: i2c-qcom-geni: Signify successful driver probe

Johan Hovold
2019-06-12T14:54:48Z

[-- Attachment #1: Type: text/plain, Size: 777 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]