On Tue, Feb 03, 2015 at 05:55:25PM +0800, Ken Xue wrote: > On Tue, 2015-02-03 at 11:53 +0200, mika.westerberg@xxxxxxxxxxxxxxx > wrote: > > On Tue, Feb 03, 2015 at 09:04:55AM +0800, Ken Xue wrote: > > > as you said, platform_drv_probe calls dev_pm_domain_attach(). but > > > platform_drv_probe just is a default probe routine. Not all platform > > > device drivers use this probe routine. so, codes here may be still > > > necessary. > > > > Are you saying that for platform devices there is some other path to get > > a driver probed, other than platform_drv_probe()? Can you point me to > > it? > >From the codes, i can see there is a possibility that drv->driver.probe > may not be set in __platform_driver_register. But i really can not point > out a use case that platform device driver without probe. > so, it is safe to remove "dev_pm_domain_attach" in > "acpi_apd_platform_notify". right? In that case, I think so, yes. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
