From: Adam Ford <hidden> Date: 2021-12-08 22:50:42
Both the i.MX8MQ and i.MX8MM have G1 and G2 decoders.
The two decoders are similar, but the imx8mm lacks the
post-processor, so they will have distinct compatible flags.
Splitting the i.MX8MQ VPU into G1 and G2 makes it easier to
control them independently since the TRM of both the i.MX8MQ and
i.MX8MM list them as distinct IP blocks. With them being split,
the power-domain can shift to the vpu-blk-ctrl which is available
on both i.MX8MQ and i.MX8MM but some of bits are different, so
they'll have separate device tree bindings.
Lastly, with the G1 and G2 operational, enable the i.MX8MM.
On the i.MX8MM, the clock speed of 600MHz was chosen to match
the default of the kernel repo from NXP and can be overwritten
by board files for anyone who under/over volts the power rail.
The repo used as the starting point was:
git://linuxtv.org/hverkuil/media_tree.git for-v5.17e
This media hantro group has been especially helpful in helping
me get up to speed on how it works.
Fluster was run on the i.MX8M Mini at 600 MHz:
./fluster.py run -d GStreamer-VP8-V4L2SL-Gst1.0
Ran 55/61 tests successfully in 8.299 secs
./fluster.py run -dGStreamer-H.264-V4L2SL-Gst1.0
Ran 90/135 tests successfully in 71.200 secs
./fluster.py run -d GStreamer-VP9-V4L2SL-Gst1.0
Ran 139/303 tests successfully in 218.079 secs
Adam Ford (7):
dt-bindings: media: nxp,imx8mq-vpu: Support split G1 and G2 nodes with
vpu-blk-ctrl
media: hantro: Allow i.MX8MQ G1 and G2 to run independently
arm64: dts: imx8mq: Enable both G1 and G2 VPU's with vpu-blk-ctrl
arm64: dts: imx8mm: Fix VPU Hanging
dt-bindings: media: nxp,imx8mq-vpu: Enable support for i.MX8M Mini
media: hantro: Add support for i.MX8MM
arm64: dts: imx8mm: Enable Hantro G1 and G2 video decoders
Lucas Stach (3):
dt-bindings: power: imx8mq: add defines for VPU blk-ctrl domains
dt-bindings: soc: add binding for i.MX8MQ VPU blk-ctrl
soc: imx: imx8m-blk-ctrl: add i.MX8MQ VPU blk-ctrl
.../bindings/media/nxp,imx8mq-vpu.yaml | 85 ++++++++++++++-----
.../soc/imx/fsl,imx8mq-vpu-blk-ctrl.yaml | 71 ++++++++++++++++
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 29 ++++++-
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 69 +++++++++------
drivers/soc/imx/imx8m-blk-ctrl.c | 68 ++++++++++++++-
drivers/staging/media/hantro/hantro_drv.c | 3 +
drivers/staging/media/hantro/hantro_hw.h | 3 +
drivers/staging/media/hantro/imx8m_vpu_hw.c | 84 +++++++++++++++---
include/dt-bindings/power/imx8mq-power.h | 3 +
9 files changed, 357 insertions(+), 58 deletions(-)
create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mq-vpu-blk-ctrl.yaml
base-commit: d1888b0bfd2ddef2e8a81505ffa200b92cc32e0c
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Adam Ford <hidden> Date: 2021-12-08 22:50:45
From: Lucas Stach <l.stach@pengutronix.de>
This adds the defines for the power domains provided by the VPU
blk-ctrl on the i.MX8MQ.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
include/dt-bindings/power/imx8mq-power.h | 3 +++
1 file changed, 3 insertions(+)
From: Adam Ford <hidden> Date: 2021-12-08 22:50:48
From: Lucas Stach <l.stach@pengutronix.de>
This adds the DT binding for the i.MX8MQ VPU blk-ctrl.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Adam Ford <redacted>
---
.../soc/imx/fsl,imx8mq-vpu-blk-ctrl.yaml | 71 +++++++++++++++++++
1 file changed, 71 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/imx/fsl,imx8mq-vpu-blk-ctrl.yaml
From: Adam Ford <hidden> Date: 2021-12-08 22:50:55
The G1 and G2 are separate decoder blocks that are enabled by the
vpu-blk-ctrl power-domain controller, which now has a proper driver.
Update the bindings to support separate nodes for the G1 and G2
decoders using the proper driver or the older unified node with
the legacy controls.
To be compatible with older DT the driver, mark certain items as
deprecated and retain the backwards compatible example.
Signed-off-by: Adam Ford <redacted>
---
.../bindings/media/nxp,imx8mq-vpu.yaml | 83 ++++++++++++++-----
1 file changed, 64 insertions(+), 19 deletions(-)
From: Rob Herring <robh@kernel.org> Date: 2021-12-09 03:08:56
On Wed, 08 Dec 2021 16:50:23 -0600, Adam Ford wrote:
The G1 and G2 are separate decoder blocks that are enabled by the
vpu-blk-ctrl power-domain controller, which now has a proper driver.
Update the bindings to support separate nodes for the G1 and G2
decoders using the proper driver or the older unified node with
the legacy controls.
To be compatible with older DT the driver, mark certain items as
deprecated and retain the backwards compatible example.
Signed-off-by: Adam Ford <redacted>
---
.../bindings/media/nxp,imx8mq-vpu.yaml | 83 ++++++++++++++-----
1 file changed, 64 insertions(+), 19 deletions(-)
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Error: Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.example.dts:62.23-27 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [scripts/Makefile.lib:373: Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.example.dt.yaml] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1413: dt_binding_check] Error 2
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1565517
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Hi,
Thanks for the patch.
On Wed, Dec 08, 2021 at 04:50:23PM -0600, Adam Ford wrote:
quoted hunk
The G1 and G2 are separate decoder blocks that are enabled by the
vpu-blk-ctrl power-domain controller, which now has a proper driver.
Update the bindings to support separate nodes for the G1 and G2
decoders using the proper driver or the older unified node with
the legacy controls.
To be compatible with older DT the driver, mark certain items as
deprecated and retain the backwards compatible example.
Signed-off-by: Adam Ford <redacted>
---
.../bindings/media/nxp,imx8mq-vpu.yaml | 83 ++++++++++++++-----
1 file changed, 64 insertions(+), 19 deletions(-)
Is it really useful to keep the deprecated binding nxp,imx8mq-vpu
as something supported by the binding file?
In other words, can we drop the deprecated binding from this file,
while keeping the support in the driver for legacy device-trees?
[..]
reg-names, interrupt-names and clock-names should be removed
given for this device there's only one of each.
This will make the binding actually quite easier, but it also
means you need to make some changes to struct hantro_variant imx8mq_vpu_g1_variant
to make it work properly.
See Rob's feedback on the SAMA5 VPU binding:
https://yhbt.net/lore/all/20210324151715.GA3070006@robh.at.kernel.org/
Also, take a look at drivers/staging/media/hantro/sama5d4_vdec_hw.c
for reference.
From: Adam Ford <hidden> Date: 2021-12-09 11:36:18
On Thu, Dec 9, 2021 at 4:26 AM Ezequiel Garcia
[off-list ref] wrote:
Hi,
Thanks for the patch.
On Wed, Dec 08, 2021 at 04:50:23PM -0600, Adam Ford wrote:
quoted
The G1 and G2 are separate decoder blocks that are enabled by the
vpu-blk-ctrl power-domain controller, which now has a proper driver.
Update the bindings to support separate nodes for the G1 and G2
decoders using the proper driver or the older unified node with
the legacy controls.
To be compatible with older DT the driver, mark certain items as
deprecated and retain the backwards compatible example.
Signed-off-by: Adam Ford <redacted>
---
.../bindings/media/nxp,imx8mq-vpu.yaml | 83 ++++++++++++++-----
1 file changed, 64 insertions(+), 19 deletions(-)
Is it really useful to keep the deprecated binding nxp,imx8mq-vpu
as something supported by the binding file?
Since I was told that the driver needed to be backwards compatible, i
wanted to make sure that any attempts to build the old device tree
would not fail
In other words, can we drop the deprecated binding from this file,
while keeping the support in the driver for legacy device-trees?
I was trying to represent both the old driver binding and the new one
at the same time. I thought that's what I was told to do.
reg-names, interrupt-names and clock-names should be removed
given for this device there's only one of each.
I attempted to remove the reg-names, but it failed to enumerate for me
when I did that.
This will make the binding actually quite easier, but it also
means you need to make some changes to struct hantro_variant imx8mq_vpu_g1_variant
to make it work properly.
See Rob's feedback on the SAMA5 VPU binding:
https://yhbt.net/lore/all/20210324151715.GA3070006@robh.at.kernel.org/
Also, take a look at drivers/staging/media/hantro/sama5d4_vdec_hw.c
for reference.
From: Rob Herring <robh@kernel.org> Date: 2021-12-10 15:36:28
On Thu, Dec 09, 2021 at 05:36:04AM -0600, Adam Ford wrote:
On Thu, Dec 9, 2021 at 4:26 AM Ezequiel Garcia
[off-list ref] wrote:
quoted
Hi,
Thanks for the patch.
On Wed, Dec 08, 2021 at 04:50:23PM -0600, Adam Ford wrote:
quoted
The G1 and G2 are separate decoder blocks that are enabled by the
vpu-blk-ctrl power-domain controller, which now has a proper driver.
Update the bindings to support separate nodes for the G1 and G2
decoders using the proper driver or the older unified node with
the legacy controls.
To be compatible with older DT the driver, mark certain items as
deprecated and retain the backwards compatible example.
Signed-off-by: Adam Ford <redacted>
---
.../bindings/media/nxp,imx8mq-vpu.yaml | 83 ++++++++++++++-----
1 file changed, 64 insertions(+), 19 deletions(-)
Is it really useful to keep the deprecated binding nxp,imx8mq-vpu
as something supported by the binding file?
Since I was told that the driver needed to be backwards compatible, i
wanted to make sure that any attempts to build the old device tree
would not fail
I'm not convinced changing the binding at all is correct. 'The driver
structure is changing and I want the binding to align with it' is not a
reason. Are G1 and G2 actually separate, independent blocks where we
could have 1 or both of them? And what about other platforms using this
block?
Even if the driver handles the old binding, a new dtb with an old kernel
is broken. It's up to the platform to care or not, but you have to
highlight that.
quoted
In other words, can we drop the deprecated binding from this file,
while keeping the support in the driver for legacy device-trees?
I was trying to represent both the old driver binding and the new one
at the same time. I thought that's what I was told to do.
I don't care so much if we have a schema for old binding. I'd rather
have warnings if the binding has not been updated. Eventually I want to
be able to test for compatibility by testing DTs with different schema
versions. We've got to get to 0 warnings first though...
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Lucas Stach <l.stach@pengutronix.de> Date: 2021-12-10 15:58:41
Am Freitag, dem 10.12.2021 um 09:36 -0600 schrieb Rob Herring:
On Thu, Dec 09, 2021 at 05:36:04AM -0600, Adam Ford wrote:
quoted
On Thu, Dec 9, 2021 at 4:26 AM Ezequiel Garcia
[off-list ref] wrote:
quoted
Hi,
Thanks for the patch.
On Wed, Dec 08, 2021 at 04:50:23PM -0600, Adam Ford wrote:
quoted
The G1 and G2 are separate decoder blocks that are enabled by the
vpu-blk-ctrl power-domain controller, which now has a proper driver.
Update the bindings to support separate nodes for the G1 and G2
decoders using the proper driver or the older unified node with
the legacy controls.
To be compatible with older DT the driver, mark certain items as
deprecated and retain the backwards compatible example.
Signed-off-by: Adam Ford <redacted>
---
.../bindings/media/nxp,imx8mq-vpu.yaml | 83 ++++++++++++++-----
1 file changed, 64 insertions(+), 19 deletions(-)
Is it really useful to keep the deprecated binding nxp,imx8mq-vpu
as something supported by the binding file?
Since I was told that the driver needed to be backwards compatible, i
wanted to make sure that any attempts to build the old device tree
would not fail
I'm not convinced changing the binding at all is correct. 'The driver
structure is changing and I want the binding to align with it' is not a
reason. Are G1 and G2 actually separate, independent blocks where we
could have 1 or both of them? And what about other platforms using this
block?
Yes, they are totally independent video decoder peripherals, handling
different codecs. While I'm not aware that there is a SKU that only
uses one of them, there is a provision in the fuses to disable either
one of the VPU peripherals, so they clearly can work independently.
Smashing them together in one DT node was a mistake IMO. Both VPUs do
not share more than a common power-domain and use the same AMBA domain
bridge to hook into to SoC NoC. On the i.MX8M Mini we have a similar
VPU subsystem, but with nested power domains, so G1, G2 and the new H1
encoder on this chip can even be powered-gated individually.
I agree that the commit message should point out that new DT + old
kernel is not a supported configuration. It isn't optimal, but IMHO a
small price to pay for the ability to handle all the i.MX8M* family VPU
subsystems in the same way with a proper blk-ctrl driver for the common
clock and reset block and the VPUs being independent peripherals.
Even if the driver handles the old binding, a new dtb with an old kernel
is broken. It's up to the platform to care or not, but you have to
highlight that.
quoted
quoted
In other words, can we drop the deprecated binding from this file,
while keeping the support in the driver for legacy device-trees?
I was trying to represent both the old driver binding and the new one
at the same time. I thought that's what I was told to do.
I don't care so much if we have a schema for old binding. I'd rather
have warnings if the binding has not been updated. Eventually I want to
be able to test for compatibility by testing DTs with different schema
versions. We've got to get to 0 warnings first though...
I'm in favor of dropping the old binding from the schema. New DTs
should clearly use the new binding and old DTs shouldn't change
anymore, so validation is less useful there.
Regards,
Lucas
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Adam Ford <hidden> Date: 2021-12-10 17:03:04
On Fri, Dec 10, 2021 at 9:58 AM Lucas Stach [off-list ref] wrote:
Am Freitag, dem 10.12.2021 um 09:36 -0600 schrieb Rob Herring:
quoted
On Thu, Dec 09, 2021 at 05:36:04AM -0600, Adam Ford wrote:
quoted
On Thu, Dec 9, 2021 at 4:26 AM Ezequiel Garcia
[off-list ref] wrote:
quoted
Hi,
Thanks for the patch.
On Wed, Dec 08, 2021 at 04:50:23PM -0600, Adam Ford wrote:
quoted
The G1 and G2 are separate decoder blocks that are enabled by the
vpu-blk-ctrl power-domain controller, which now has a proper driver.
Update the bindings to support separate nodes for the G1 and G2
decoders using the proper driver or the older unified node with
the legacy controls.
To be compatible with older DT the driver, mark certain items as
deprecated and retain the backwards compatible example.
Signed-off-by: Adam Ford <redacted>
---
.../bindings/media/nxp,imx8mq-vpu.yaml | 83 ++++++++++++++-----
1 file changed, 64 insertions(+), 19 deletions(-)
Is it really useful to keep the deprecated binding nxp,imx8mq-vpu
as something supported by the binding file?
Since I was told that the driver needed to be backwards compatible, i
wanted to make sure that any attempts to build the old device tree
would not fail
I'm not convinced changing the binding at all is correct. 'The driver
structure is changing and I want the binding to align with it' is not a
reason. Are G1 and G2 actually separate, independent blocks where we
could have 1 or both of them? And what about other platforms using this
block?
Yes, they are totally independent video decoder peripherals, handling
different codecs. While I'm not aware that there is a SKU that only
uses one of them, there is a provision in the fuses to disable either
one of the VPU peripherals, so they clearly can work independently.
Smashing them together in one DT node was a mistake IMO. Both VPUs do
not share more than a common power-domain and use the same AMBA domain
bridge to hook into to SoC NoC. On the i.MX8M Mini we have a similar
VPU subsystem, but with nested power domains, so G1, G2 and the new H1
encoder on this chip can even be powered-gated individually.
I agree that the commit message should point out that new DT + old
kernel is not a supported configuration. It isn't optimal, but IMHO a
small price to pay for the ability to handle all the i.MX8M* family VPU
subsystems in the same way with a proper blk-ctrl driver for the common
clock and reset block and the VPUs being independent peripherals.
quoted
Even if the driver handles the old binding, a new dtb with an old kernel
is broken. It's up to the platform to care or not, but you have to
highlight that.
quoted
quoted
In other words, can we drop the deprecated binding from this file,
while keeping the support in the driver for legacy device-trees?
I was trying to represent both the old driver binding and the new one
at the same time. I thought that's what I was told to do.
I don't care so much if we have a schema for old binding. I'd rather
have warnings if the binding has not been updated. Eventually I want to
be able to test for compatibility by testing DTs with different schema
versions. We've got to get to 0 warnings first though...
I'm in favor of dropping the old binding from the schema. New DTs
should clearly use the new binding and old DTs shouldn't change
anymore, so validation is less useful there.
I wonder if it makes sense to have a more standardized hantro schema
for all the users instead of one dedicated to each platform using a
hantro driver. The unified schema could have all the various
compatible flags so the driver still knows which features are
enabled/disabled and it's very clear who all the users are for it. I
would think it could cover both the encoder and decoder variants as
well. We do something similar for 8250 serial ports.
If so, can someone from the media group suggest the best one to
follow? Ezequiel suggested I look at the sama5d4-vdec to help reduce
some clutter in the driver. If that binding is good enough, should I
just add the compatible flags to that and potentially rename it.
adam
I'm in favor of dropping the old binding from the schema. New DTs
should clearly use the new binding and old DTs shouldn't change
anymore, so validation is less useful there.
I wonder if it makes sense to have a more standardized hantro schema
for all the users instead of one dedicated to each platform using a
hantro driver. The unified schema could have all the various
compatible flags so the driver still knows which features are
enabled/disabled and it's very clear who all the users are for it. I
would think it could cover both the encoder and decoder variants as
well. We do something similar for 8250 serial ports.
If so, can someone from the media group suggest the best one to
follow? Ezequiel suggested I look at the sama5d4-vdec to help reduce
some clutter in the driver. If that binding is good enough, should I
just add the compatible flags to that and potentially rename it.
A unified schema might sound elegant and compelling, but I suspect
it can bite us down the road, due to differences in the platform integration.
Seems we are all on-board going forward with a patch similar to this one,
but also dropping the deprecated binding from the schema (while of course
still supporting old DTBs on new kernels).
Rob's suggestion about having a warning in the platform if the binding has
not been updated, sounds like very useful too.
Keep in mind v5.16-rc5 is near, which means we still have a few weeks to
discuss this patch, until the next linux-media merge season.
Thanks,
Ezequiel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Adam Ford <hidden> Date: 2021-12-08 22:50:57
From: Lucas Stach <l.stach@pengutronix.de>
This adds the necessary bits to drive the VPU blk-ctrl on the i.MX8MQ, to
avoid putting more of this functionality into the decoder driver.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Adam Ford <redacted>
---
drivers/soc/imx/imx8m-blk-ctrl.c | 68 +++++++++++++++++++++++++++++++-
1 file changed, 67 insertions(+), 1 deletion(-)
From: Adam Ford <hidden> Date: 2021-12-08 22:51:00
With the Hantro G1 and G2 now setup to run independently, update
the device tree to allow both to operate. This requires the
vpu-blk-ctrl node to be configured. Since vpu-blk-ctrl needs
certain clock enabled to handle the gating of the G1 and G2
fuses, the clock-parents and clock-rates for the various VPU's
to be moved into the pgc_vpu because they cannot get re-parented
once enabled, and the pgc_vpu is the highest in the chain.
Signed-off-by: Adam Ford <redacted>
---
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 69 +++++++++++++++--------
1 file changed, 45 insertions(+), 24 deletions(-)
From: Adam Ford <hidden> Date: 2021-12-08 22:51:02
The VPU in the i.MX8MQ is really the combination of Hantro G1 and
Hantro G2. With the updated vpu-blk-ctrl, the power domains system
can enable and disable them separately as well as pull them out of
reset. This simplifies the code and lets them run independently
while still retaining backwards compatibility with older device
trees for those using G1.
Signed-off-by: Adam Ford <redacted>
---
drivers/staging/media/hantro/hantro_drv.c | 1 +
drivers/staging/media/hantro/hantro_hw.h | 1 +
drivers/staging/media/hantro/imx8m_vpu_hw.c | 56 ++++++++++++++++-----
3 files changed, 45 insertions(+), 13 deletions(-)
From: Adam Ford <hidden> Date: 2021-12-08 22:51:10
The i.MX8M mini appears to have a similar G1 and G2 decoder but the
post-procesing isn't present. Add compatible flags to support
G1 and G2 without post-processing.
Signed-off-by: Adam Ford <redacted>
---
Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.yaml | 2 ++
1 file changed, 2 insertions(+)
From: Rob Herring <robh@kernel.org> Date: 2021-12-15 16:53:26
On Wed, Dec 08, 2021 at 04:50:27PM -0600, Adam Ford wrote:
quoted hunk
The i.MX8M mini appears to have a similar G1 and G2 decoder but the
post-procesing isn't present. Add compatible flags to support
G1 and G2 without post-processing.
Signed-off-by: Adam Ford <redacted>
---
Documentation/devicetree/bindings/media/nxp,imx8mq-vpu.yaml | 2 ++
1 file changed, 2 insertions(+)
From: Adam Ford <hidden> Date: 2021-12-08 22:51:13
The vpumix power domain has a reset assigned to it, however
when used, it causes a system hang. Testing has shown that
it does not appear to be needed anywhere.
Fixes: d39d4bb15310 ("arm64: dts: imx8mm: add GPC node")
Signed-off-by: Adam Ford <redacted>
---
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 1 -
1 file changed, 1 deletion(-)
From: Adam Ford <hidden> Date: 2021-12-08 22:51:15
The i.MX8MM has a G1 and G2 video decoder, so add support in
the driver for it with the post-processing removed.
Signed-off-by: Adam Ford <redacted>
---
drivers/staging/media/hantro/hantro_drv.c | 2 ++
drivers/staging/media/hantro/hantro_hw.h | 2 ++
drivers/staging/media/hantro/imx8m_vpu_hw.c | 28 +++++++++++++++++++++
3 files changed, 32 insertions(+)
From: Adam Ford <hidden> Date: 2021-12-08 22:51:19
There are two decoders on the i.MX8M Mini controlled by the
vpu-blk-ctrl. The G1 supports H264 and VP8 while the
G2 support HEVC and VP9.
Signed-off-by: Adam Ford <redacted>
---
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 28 +++++++++++++++++++++++
1 file changed, 28 insertions(+)