[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4f2a2dc5-f145-ce20-eebe-08a6e084ef66@cogentembedded.com>
Date: Mon, 13 Dec 2021 23:13:50 +0300
From: Nikita Yushchenko <nikita.yoush@...entembedded.com>
To: Kieran Bingham <kieran.bingham+renesas@...asonboard.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>
Cc: linux-media@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Koji Matsuoka <koji.matsuoka.xm@...esas.com>
Subject: Re: [PATCH] media: vsp1: mask interrupts before enabling
Hi.
Now I'm finally looking at this again.
> I think I would rather see the code to reset them done in
> vsp1_reset_wpf(), rather than in probe directly as that is what we are
> doing, and is I believe already in the call path.
Could you please explain, how that is intended to be called on the probe path?
As far as can read from the code, vsp1_reset_wpf() is only called from vsp1_device_init(), which in turn
is called only from PM resume hook and only if vsp1->info is already set. However, in the probe path,
pm_runtime_enable() is called before vsp1->info is set.
Nikita
Powered by blists - more mailing lists