Hi Niklas, On Thu, May 16, 2019 at 3:46 AM Niklas Söderlund <niklas.soderlund+renesas@xxxxxxxxxxxx> wrote: > The driver does not implement runtime resume and suspend function so > there is little point in trying to call them. This is a leftover from > the drivers soc_camera beginnings. > > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@xxxxxxxxxxxx> > Reviewed-by: Ulrich Hecht <uli+renesas@xxxxxxxx> > --- > drivers/media/platform/rcar-vin/rcar-v4l2.c | 5 ----- > 1 file changed, 5 deletions(-) > > diff --git a/drivers/media/platform/rcar-vin/rcar-v4l2.c b/drivers/media/platform/rcar-vin/rcar-v4l2.c > index 7cbdcbf9b090c638..b821ea01786eb1ff 100644 > --- a/drivers/media/platform/rcar-vin/rcar-v4l2.c > +++ b/drivers/media/platform/rcar-vin/rcar-v4l2.c > @@ -798,9 +798,6 @@ static int rvin_initialize_device(struct file *file) > return ret; > > pm_runtime_enable(&vin->vdev.dev); > - ret = pm_runtime_resume(&vin->vdev.dev); Please pardon my ignorance, but which device is vin->vdev.dev? Who calls pm_runtime_get_sync() on it, and where? I see this function calls rvin_power_on(vin->v4l2_dev.dev) (before the call to pm_runtime_enable()), but presumably that's a different device? Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds