On Thu, Nov 27, 2014 at 1:00 AM, Sunil Shahu <sunil.rockon@xxxxxxxx> wrote: > Hi Daniel, > Thanks, dump_stack() is what I needed. > > Hi Subin, > Thanks for the snapshot. > > Also, I am attaching a graph for what I understood after following > dump_stack(). > > Please let me know if there is any issue with the flow. > > Thanks, > Sunil. > > > > On Saturday, 22 November 2014 9:04 AM, subin gangadharan > <subingangadharan@xxxxxxxxx> wrote: > > > Hi Sunil, > >>>I am still not able to locate from WHERE this probe function is called and >>> WHO calls it? > > I can try to give you a snapshot of the function call trace. But if > you really want to get in depth detail, as Greg said look at the code > driver/base. > > driver_register > ->bus_add_driver->driver_attach->__driver_attach->driver_probe_device->really_probe->drv->probe > > Basically when you register your platform driver, the platform > bus(platform_bus_type) will scan for the matching device. If you look > at the platform_bus_type structure you can find the match function > which does the matching of driver and device. Once it's found the > right device, it will attach the driver to the device.Look at the > function driver_attach. And if you look at the > platform_driver_register function, you can see that > "platform_drv_probe" function is assigned to driver.probe function. > And this probe function will finally call your registered platform > driver probe function. > > Hope this helps. > > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@xxxxxxxxxxxxxxxxx > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > Hi Sunil, Thanks for the nice detailed snap shot. Subin _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
