Return-Path: Message-ID: <1524720598.12322.37.camel@mtkswgap22> Subject: Re: [PATCH v1 2/7] serdev: add dev_pm_domain_attach|detach() From: Sean Wang To: Marcel Holtmann CC: Rob Herring , Mark Rutland , Johan Hedberg , devicetree , Bluez mailing list , linux-arm-kernel , , LKML , Rob Herring , "Ulf Hansson" , Greg Kroah-Hartman , Jiri Slaby , Date: Thu, 26 Apr 2018 13:29:58 +0800 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Sender: linux-serial-owner@vger.kernel.org List-ID: On Tue, 2018-04-03 at 12:29 +0200, Marcel Holtmann wrote: > Hi Sean, > > > In order to open up the required power gate before any operation can be > > effectively performed over the serial bus between CPU and serdev, it's > > clearly essential to add common attach functions for PM domains to serdev > > at the probe phase. > > > > Similarly, the relevant dettach function for the PM domains should be > > properly and reversely added at the remove phase. > > > > Signed-off-by: Sean Wang > > Cc: Rob Herring > > Cc: Ulf Hansson > > Cc: Greg Kroah-Hartman > > Cc: Jiri Slaby > > Cc: linux-serial@vger.kernel.org > > --- > > drivers/tty/serdev/core.c | 14 +++++++++++++- > > 1 file changed, 13 insertions(+), 1 deletion(-) > > > > diff --git a/drivers/tty/serdev/core.c b/drivers/tty/serdev/core.c > > index df93b72..c93d8ee 100644 > > --- a/drivers/tty/serdev/core.c > > +++ b/drivers/tty/serdev/core.c > > @@ -13,6 +13,7 @@ > > #include > > #include > > #include > > +#include > > #include > > #include > > > > @@ -330,8 +331,16 @@ EXPORT_SYMBOL_GPL(serdev_device_set_tiocm); > > static int serdev_drv_probe(struct device *dev) > > { > > const struct serdev_device_driver *sdrv = to_serdev_device_driver(dev->driver); > > + int ret; > > + > > + ret = dev_pm_domain_attach(dev, true); > > + if (ret != -EPROBE_DEFER) { > > + ret = sdrv->probe(to_serdev_device(dev)); > > + if (ret) > > + dev_pm_domain_detach(dev, true); > > + } > > so if this is deferred, when does the serdev device gets probed? > driver probe deferral mechanism is supported in driver core deferred_probe_initcall makes sure that deferred probing is delayed until late_initcall time. Below is a few of word I got from drivers/base/core.c I thought it helps to understand the mechanism in complete picture * If a required resource is not available yet, a driver can request probing to be deferred by returning -EPROBE_DEFER from its probe hook. * A driver returning -EPROBE_DEFER causes the device to be added to the pending list. A successful driver probe will trigger moving all devices from the pending to the active list so that the workqueue will eventually retry them. > > > > - return sdrv->probe(to_serdev_device(dev)); > > + return ret; > > } > > > > static int serdev_drv_remove(struct device *dev) > > @@ -339,6 +348,9 @@ static int serdev_drv_remove(struct device *dev) > > const struct serdev_device_driver *sdrv = to_serdev_device_driver(dev->driver); > > if (sdrv->remove) > > sdrv->remove(to_serdev_device(dev)); > > + > > + dev_pm_domain_detach(dev, true); > > + > > return 0; > > } > > Regards > > Marcel >