remoteproc/wkup_m3: Use reset control driver if available
authorTony Lindgren <tony@atomide.com>
Mon, 16 Nov 2020 10:57:13 +0000 (12:57 +0200)
committerTony Lindgren <tony@atomide.com>
Mon, 16 Nov 2020 10:57:40 +0000 (12:57 +0200)
commit57df7e370d2ab83a64c07acd157acfed4169f114
tree5f3642f4f085ba810a03c95a3dcc9413c7cb87c4
parent74033131d2467fda6b76ba10bc80a75fb47e03d1
remoteproc/wkup_m3: Use reset control driver if available

In order to move wkup_m3 to probe without platform data, let's add
support for using optional reset control driver if configured in the
dts. With this change and the related dts change, we can start
dropping the platform data for am335x.

And once wkup_m3 no longer needs platform data, we can simply drop the
related legacy reset platform data callbacks from wkup_m3 driver later
on after also am437x no longer depends on it.

Cc: linux-remoteproc@vger.kernel.org
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Dave Gerlach <d-gerlach@ti.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Suman Anna <s-anna@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
drivers/remoteproc/wkup_m3_rproc.c