This is just an example of how a serdev driver could go about to allow aggressive controller runtime PM by dropping the RPM reference taken by serdev core in serdev_device_open(). Note that for most GNSS devices this does not make any sense, as allowing the controller to suspend this way would cause the first message of every report burst to be corrupted (and discarded). This one applies on top of the GNSS series available here: https://lkml.kernel.org/r/20180424163458.11947-1-johan@xxxxxxxxxx Not-Signed-off-by: Johan Hovold <johan@xxxxxxxxxx> --- drivers/gnss/sirf.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/gnss/sirf.c b/drivers/gnss/sirf.c index 497f8eb8467f..31b2cbccd194 100644 --- a/drivers/gnss/sirf.c +++ b/drivers/gnss/sirf.c @@ -57,6 +57,9 @@ static int sirf_open(struct gnss_device *gdev) goto err_close; } + /* Allow aggresive controller runtime PM. */ + pm_runtime_put(&serdev->ctrl->dev); + return 0; err_close: @@ -70,6 +73,9 @@ static void sirf_close(struct gnss_device *gdev) struct sirf_data *data = gnss_get_drvdata(gdev); struct serdev_device *serdev = data->serdev; + /* Balance the put in open() */ + pm_runtime_get(&serdev->ctrl->dev); + serdev_device_close(serdev); pm_runtime_put(&serdev->dev); -- 2.17.0 -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
