[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210211115003.249367-1-benjamin.gaignard@collabora.com>
Date: Thu, 11 Feb 2021 12:49:59 +0100
From: Benjamin Gaignard <benjamin.gaignard@...labora.com>
To: p.zabel@...gutronix.de, robh+dt@...nel.org, shawnguo@...nel.org,
s.hauer@...gutronix.de, festevam@...il.com, ezequiel@...labora.com,
mchehab@...nel.org, gregkh@...uxfoundation.org
Cc: kernel@...gutronix.de, linux-imx@....com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
linux-rockchip@...ts.infradead.org, devel@...verdev.osuosl.org,
kernel@...labora.com, benjamin.gaignard@...labora.com
Subject: [PATCH 0/4] Reset driver for IMX8MQ VPU hardware block
The two VPUs inside IMX8MQ share the same control block which can be see
as a reset hardware block.
In order to be able to add the second VPU (for HECV decoding) it will be
more handy if the both VPU drivers instance don't have to share the
control block registers. This lead to implement it as an independ reset
driver and to change the VPU driver to use it.
Benjamin Gaignard (4):
dt-bindings: reset: IMX8MQ VPU reset
reset: Add reset driver for IMX8MQ VPU block
media: hantro: Use reset driver
arm64: dts: imx8mq: Use reset driver for VPU hardware block
.../bindings/reset/fsl,imx8mq-vpu-reset.yaml | 54 ++++++
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 31 +++-
drivers/reset/Kconfig | 8 +
drivers/reset/Makefile | 1 +
drivers/reset/reset-imx8mq-vpu.c | 169 ++++++++++++++++++
drivers/staging/media/hantro/Kconfig | 1 +
drivers/staging/media/hantro/imx8m_vpu_hw.c | 61 ++-----
include/dt-bindings/reset/imx8mq-vpu-reset.h | 16 ++
8 files changed, 285 insertions(+), 56 deletions(-)
create mode 100644 Documentation/devicetree/bindings/reset/fsl,imx8mq-vpu-reset.yaml
create mode 100644 drivers/reset/reset-imx8mq-vpu.c
create mode 100644 include/dt-bindings/reset/imx8mq-vpu-reset.h
--
2.25.1
Powered by blists - more mailing lists