All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Ezequiel Garcia <ezequiel@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	p.zabel@pengutronix.de, mchehab@kernel.org, robh+dt@kernel.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	gregkh@linuxfoundation.org, mripard@kernel.org,
	paul.kocialkowski@bootlin.com, wens@csie.org,
	jernej.skrabec@siol.net, krzk@kernel.org, shengjiu.wang@nxp.com,
	adrian.ratiu@collabora.com, aisheng.dong@nxp.com,
	peng.fan@nxp.com, Anson.Huang@nxp.com, hverkuil-cisco@xs4all.nl
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	kernel@collabora.com, linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v1 03/18] arm64: dts: imx8mq-evk: add reserve memory node for CMA region
Date: Thu, 18 Feb 2021 11:15:13 +0100	[thread overview]
Message-ID: <c029c980937ab50847bd0fcf86501e85bdb91fd3.camel@pengutronix.de> (raw)
In-Reply-To: <ab14f5a0bde2bdcd4bb0128f76e5a3ba8e7b0894.camel@collabora.com>

Am Mittwoch, dem 17.02.2021 um 16:39 -0300 schrieb Ezequiel Garcia:
> Hi Benjamin,
> 
> On Wed, 2021-02-17 at 09:02 +0100, Benjamin Gaignard wrote:
> > Define allocation range for the default CMA region.
> > 
> > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> > Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> 
> Despite it seems like I signed-off this one...
> 
> > Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
> > ---
> >  arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 15 +++++++++++++++
> >  1 file changed, 15 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts b/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > index 85b045253a0e..047dfd4a1ffd 100644
> > --- a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > +++ b/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > @@ -21,6 +21,21 @@ memory@40000000 {
> >                 reg = <0x00000000 0x40000000 0 0xc0000000>;
> >         };
> > 
> >  
> > +       resmem: reserved-memory {
> > +               #address-cells = <2>;
> > +               #size-cells = <2>;
> > +               ranges;
> > +
> > +               /* global autoconfigured region for contiguous allocations */
> > +               linux,cma {
> > +                       compatible = "shared-dma-pool";
> > +                       reusable;
> > +                       size = <0 0x3c000000>;
> > +                       alloc-ranges = <0 0x40000000 0 0x40000000>;
> > +                       linux,cma-default;
> > +               };
> 
> ... I'm not a fan of the change :)
> 
> Hopefully someone from NXP can provide some insight here?
> 
> If it's absolutely needed for the VPU, then I guess it should
> be 1) very well documented and 2) moved to the top-lovel dtsi.
> 
> But if we can drop it, that'd be nicer.

What's the justification for this CMA area?

I could only imagine the DMA addressing restrictions on the platform.
DMA masters on the i.MX8MQ can not access memory beyond the 4GB mark
and 1GB of address space is reserved for MMIO, so if you have 4GB
installed the upper 1GB of DRAM is only accessible to the CPU. But this
restriction is already properly communicated to the Linux DMA framework
by the dma-ranges in the top level SoC bus node in the DT, so I don't
think this CMA setup is necessary.

Regards,
Lucas


WARNING: multiple messages have this Message-ID (diff)
From: Lucas Stach <l.stach@pengutronix.de>
To: Ezequiel Garcia <ezequiel@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	p.zabel@pengutronix.de, mchehab@kernel.org,  robh+dt@kernel.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	 kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	 gregkh@linuxfoundation.org, mripard@kernel.org,
	paul.kocialkowski@bootlin.com,  wens@csie.org,
	jernej.skrabec@siol.net, krzk@kernel.org, shengjiu.wang@nxp.com,
	 adrian.ratiu@collabora.com, aisheng.dong@nxp.com,
	peng.fan@nxp.com,  Anson.Huang@nxp.com, hverkuil-cisco@xs4all.nl
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	kernel@collabora.com, linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v1 03/18] arm64: dts: imx8mq-evk: add reserve memory node for CMA region
Date: Thu, 18 Feb 2021 11:15:13 +0100	[thread overview]
Message-ID: <c029c980937ab50847bd0fcf86501e85bdb91fd3.camel@pengutronix.de> (raw)
In-Reply-To: <ab14f5a0bde2bdcd4bb0128f76e5a3ba8e7b0894.camel@collabora.com>

Am Mittwoch, dem 17.02.2021 um 16:39 -0300 schrieb Ezequiel Garcia:
> Hi Benjamin,
> 
> On Wed, 2021-02-17 at 09:02 +0100, Benjamin Gaignard wrote:
> > Define allocation range for the default CMA region.
> > 
> > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> > Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> 
> Despite it seems like I signed-off this one...
> 
> > Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
> > ---
> >  arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 15 +++++++++++++++
> >  1 file changed, 15 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts b/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > index 85b045253a0e..047dfd4a1ffd 100644
> > --- a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > +++ b/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > @@ -21,6 +21,21 @@ memory@40000000 {
> >                 reg = <0x00000000 0x40000000 0 0xc0000000>;
> >         };
> > 
> >  
> > +       resmem: reserved-memory {
> > +               #address-cells = <2>;
> > +               #size-cells = <2>;
> > +               ranges;
> > +
> > +               /* global autoconfigured region for contiguous allocations */
> > +               linux,cma {
> > +                       compatible = "shared-dma-pool";
> > +                       reusable;
> > +                       size = <0 0x3c000000>;
> > +                       alloc-ranges = <0 0x40000000 0 0x40000000>;
> > +                       linux,cma-default;
> > +               };
> 
> ... I'm not a fan of the change :)
> 
> Hopefully someone from NXP can provide some insight here?
> 
> If it's absolutely needed for the VPU, then I guess it should
> be 1) very well documented and 2) moved to the top-lovel dtsi.
> 
> But if we can drop it, that'd be nicer.

What's the justification for this CMA area?

I could only imagine the DMA addressing restrictions on the platform.
DMA masters on the i.MX8MQ can not access memory beyond the 4GB mark
and 1GB of address space is reserved for MMIO, so if you have 4GB
installed the upper 1GB of DRAM is only accessible to the CPU. But this
restriction is already properly communicated to the Linux DMA framework
by the dma-ranges in the top level SoC bus node in the DT, so I don't
think this CMA setup is necessary.

Regards,
Lucas

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

WARNING: multiple messages have this Message-ID (diff)
From: Lucas Stach <l.stach@pengutronix.de>
To: Ezequiel Garcia <ezequiel@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	p.zabel@pengutronix.de, mchehab@kernel.org,  robh+dt@kernel.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	 kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	 gregkh@linuxfoundation.org, mripard@kernel.org,
	paul.kocialkowski@bootlin.com,  wens@csie.org,
	jernej.skrabec@siol.net, krzk@kernel.org, shengjiu.wang@nxp.com,
	 adrian.ratiu@collabora.com, aisheng.dong@nxp.com,
	peng.fan@nxp.com,  Anson.Huang@nxp.com, hverkuil-cisco@xs4all.nl
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	kernel@collabora.com, linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v1 03/18] arm64: dts: imx8mq-evk: add reserve memory node for CMA region
Date: Thu, 18 Feb 2021 11:15:13 +0100	[thread overview]
Message-ID: <c029c980937ab50847bd0fcf86501e85bdb91fd3.camel@pengutronix.de> (raw)
In-Reply-To: <ab14f5a0bde2bdcd4bb0128f76e5a3ba8e7b0894.camel@collabora.com>

Am Mittwoch, dem 17.02.2021 um 16:39 -0300 schrieb Ezequiel Garcia:
> Hi Benjamin,
> 
> On Wed, 2021-02-17 at 09:02 +0100, Benjamin Gaignard wrote:
> > Define allocation range for the default CMA region.
> > 
> > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> > Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> 
> Despite it seems like I signed-off this one...
> 
> > Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
> > ---
> >  arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 15 +++++++++++++++
> >  1 file changed, 15 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts b/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > index 85b045253a0e..047dfd4a1ffd 100644
> > --- a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > +++ b/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > @@ -21,6 +21,21 @@ memory@40000000 {
> >                 reg = <0x00000000 0x40000000 0 0xc0000000>;
> >         };
> > 
> >  
> > +       resmem: reserved-memory {
> > +               #address-cells = <2>;
> > +               #size-cells = <2>;
> > +               ranges;
> > +
> > +               /* global autoconfigured region for contiguous allocations */
> > +               linux,cma {
> > +                       compatible = "shared-dma-pool";
> > +                       reusable;
> > +                       size = <0 0x3c000000>;
> > +                       alloc-ranges = <0 0x40000000 0 0x40000000>;
> > +                       linux,cma-default;
> > +               };
> 
> ... I'm not a fan of the change :)
> 
> Hopefully someone from NXP can provide some insight here?
> 
> If it's absolutely needed for the VPU, then I guess it should
> be 1) very well documented and 2) moved to the top-lovel dtsi.
> 
> But if we can drop it, that'd be nicer.

What's the justification for this CMA area?

I could only imagine the DMA addressing restrictions on the platform.
DMA masters on the i.MX8MQ can not access memory beyond the 4GB mark
and 1GB of address space is reserved for MMIO, so if you have 4GB
installed the upper 1GB of DRAM is only accessible to the CPU. But this
restriction is already properly communicated to the Linux DMA framework
by the dma-ranges in the top level SoC bus node in the DT, so I don't
think this CMA setup is necessary.

Regards,
Lucas


_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Lucas Stach <l.stach@pengutronix.de>
To: Ezequiel Garcia <ezequiel@collabora.com>,
	Benjamin Gaignard <benjamin.gaignard@collabora.com>,
	p.zabel@pengutronix.de, mchehab@kernel.org,  robh+dt@kernel.org,
	shawnguo@kernel.org, s.hauer@pengutronix.de,
	 kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	 gregkh@linuxfoundation.org, mripard@kernel.org,
	paul.kocialkowski@bootlin.com,  wens@csie.org,
	jernej.skrabec@siol.net, krzk@kernel.org, shengjiu.wang@nxp.com,
	 adrian.ratiu@collabora.com, aisheng.dong@nxp.com,
	peng.fan@nxp.com,  Anson.Huang@nxp.com, hverkuil-cisco@xs4all.nl
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	kernel@collabora.com, linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v1 03/18] arm64: dts: imx8mq-evk: add reserve memory node for CMA region
Date: Thu, 18 Feb 2021 11:15:13 +0100	[thread overview]
Message-ID: <c029c980937ab50847bd0fcf86501e85bdb91fd3.camel@pengutronix.de> (raw)
In-Reply-To: <ab14f5a0bde2bdcd4bb0128f76e5a3ba8e7b0894.camel@collabora.com>

Am Mittwoch, dem 17.02.2021 um 16:39 -0300 schrieb Ezequiel Garcia:
> Hi Benjamin,
> 
> On Wed, 2021-02-17 at 09:02 +0100, Benjamin Gaignard wrote:
> > Define allocation range for the default CMA region.
> > 
> > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@collabora.com>
> > Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> 
> Despite it seems like I signed-off this one...
> 
> > Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
> > ---
> >  arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 15 +++++++++++++++
> >  1 file changed, 15 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts b/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > index 85b045253a0e..047dfd4a1ffd 100644
> > --- a/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > +++ b/arch/arm64/boot/dts/freescale/imx8mq-evk.dts
> > @@ -21,6 +21,21 @@ memory@40000000 {
> >                 reg = <0x00000000 0x40000000 0 0xc0000000>;
> >         };
> > 
> >  
> > +       resmem: reserved-memory {
> > +               #address-cells = <2>;
> > +               #size-cells = <2>;
> > +               ranges;
> > +
> > +               /* global autoconfigured region for contiguous allocations */
> > +               linux,cma {
> > +                       compatible = "shared-dma-pool";
> > +                       reusable;
> > +                       size = <0 0x3c000000>;
> > +                       alloc-ranges = <0 0x40000000 0 0x40000000>;
> > +                       linux,cma-default;
> > +               };
> 
> ... I'm not a fan of the change :)
> 
> Hopefully someone from NXP can provide some insight here?
> 
> If it's absolutely needed for the VPU, then I guess it should
> be 1) very well documented and 2) moved to the top-lovel dtsi.
> 
> But if we can drop it, that'd be nicer.

What's the justification for this CMA area?

I could only imagine the DMA addressing restrictions on the platform.
DMA masters on the i.MX8MQ can not access memory beyond the 4GB mark
and 1GB of address space is reserved for MMIO, so if you have 4GB
installed the upper 1GB of DRAM is only accessible to the CPU. But this
restriction is already properly communicated to the Linux DMA framework
by the dma-ranges in the top level SoC bus node in the DT, so I don't
think this CMA setup is necessary.

Regards,
Lucas


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-02-18 11:50 UTC|newest]

Thread overview: 188+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  8:02 [PATCH v1 00/18] Add HANTRO G2/HEVC decoder support for IMX8MQ Benjamin Gaignard
2021-02-17  8:02 ` Benjamin Gaignard
2021-02-17  8:02 ` Benjamin Gaignard
2021-02-17  8:02 ` Benjamin Gaignard
2021-02-17  8:02 ` [PATCH v1 01/18] include: media: hevc: Add scaling and decode params controls Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02 ` [PATCH v1 02/18] media: hantro: Define HEVC codec profiles and supported features Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17 19:31   ` Ezequiel Garcia
2021-02-17 19:31     ` Ezequiel Garcia
2021-02-17 19:31     ` Ezequiel Garcia
2021-02-17 19:31     ` Ezequiel Garcia
2021-02-17  8:02 ` [PATCH v1 03/18] arm64: dts: imx8mq-evk: add reserve memory node for CMA region Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17 19:39   ` Ezequiel Garcia
2021-02-17 19:39     ` Ezequiel Garcia
2021-02-17 19:39     ` Ezequiel Garcia
2021-02-17 19:39     ` Ezequiel Garcia
2021-02-18 10:15     ` Lucas Stach [this message]
2021-02-18 10:15       ` Lucas Stach
2021-02-18 10:15       ` Lucas Stach
2021-02-18 10:15       ` Lucas Stach
2021-02-18 10:45     ` Dan Carpenter
2021-02-18 10:45       ` Dan Carpenter
2021-02-18 10:45       ` Dan Carpenter
2021-02-18 10:45       ` Dan Carpenter
2021-02-17  8:02 ` [PATCH v1 04/18] media: hevc: add structures for hevc codec Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17 19:54   ` Ezequiel Garcia
2021-02-17 19:54     ` Ezequiel Garcia
2021-02-17 19:54     ` Ezequiel Garcia
2021-02-17 19:54     ` Ezequiel Garcia
2021-02-17  8:02 ` [PATCH v1 05/18] media: controls: Add control for HEVC codec Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17 19:58   ` Ezequiel Garcia
2021-02-17 19:58     ` Ezequiel Garcia
2021-02-17 19:58     ` Ezequiel Garcia
2021-02-17 19:58     ` Ezequiel Garcia
2021-02-17  8:02 ` [PATCH v1 06/18] media: hantro: Make sure that ctx->codex_ops is set Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17 20:11   ` Ezequiel Garcia
2021-02-17 20:11     ` Ezequiel Garcia
2021-02-17 20:11     ` Ezequiel Garcia
2021-02-17 20:11     ` Ezequiel Garcia
2021-02-18 10:53   ` Dan Carpenter
2021-02-18 10:53     ` Dan Carpenter
2021-02-18 10:53     ` Dan Carpenter
2021-02-18 10:53     ` Dan Carpenter
2021-02-17  8:02 ` [PATCH v1 07/18] media: hantro: Add a field to distinguish the hardware versions Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17 20:15   ` Ezequiel Garcia
2021-02-17 20:15     ` Ezequiel Garcia
2021-02-17 20:15     ` Ezequiel Garcia
2021-02-17 20:15     ` Ezequiel Garcia
2021-02-18 10:55   ` Dan Carpenter
2021-02-18 10:55     ` Dan Carpenter
2021-02-18 10:55     ` Dan Carpenter
2021-02-18 10:55     ` Dan Carpenter
2021-02-17  8:02 ` [PATCH v1 08/18] media: hantro: Add HEVC structures Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02 ` [PATCH v1 09/18] media: hantro: move hantro_needs_postproc function Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-18 10:59   ` Dan Carpenter
2021-02-18 10:59     ` Dan Carpenter
2021-02-18 10:59     ` Dan Carpenter
2021-02-18 10:59     ` Dan Carpenter
2021-02-17  8:02 ` [PATCH v1 10/18] media: hantro: Add helper functions for buffer information Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17 20:31   ` Ezequiel Garcia
2021-02-17 20:31     ` Ezequiel Garcia
2021-02-17 20:31     ` Ezequiel Garcia
2021-02-17 20:31     ` Ezequiel Garcia
2021-02-17  8:02 ` [PATCH v1 11/18] media: hantro: Add helper function for auxiliary buffers allocation Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17  8:02   ` Benjamin Gaignard
2021-02-17 20:42   ` Ezequiel Garcia
2021-02-17 20:42     ` Ezequiel Garcia
2021-02-17 20:42     ` Ezequiel Garcia
2021-02-17 20:42     ` Ezequiel Garcia
2021-02-18 14:51     ` Benjamin Gaignard
2021-02-18 14:51       ` Benjamin Gaignard
2021-02-18 14:51       ` Benjamin Gaignard
2021-02-18 14:51       ` Benjamin Gaignard
2021-02-17  8:03 ` [PATCH v1 12/18] media: uapi: Add a control for HANTRO driver Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03 ` [PATCH v1 13/18] media: hantro: Introduce G2/HEVC decoder Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17 20:45   ` Ezequiel Garcia
2021-02-17 20:45     ` Ezequiel Garcia
2021-02-17 20:45     ` Ezequiel Garcia
2021-02-17 20:45     ` Ezequiel Garcia
2021-02-18 10:43     ` Benjamin Gaignard
2021-02-18 10:43       ` Benjamin Gaignard
2021-02-18 10:43       ` Benjamin Gaignard
2021-02-18 10:43       ` Benjamin Gaignard
2021-02-18 11:47   ` Dan Carpenter
2021-02-18 11:47     ` Dan Carpenter
2021-02-18 11:47     ` Dan Carpenter
2021-02-18 11:47     ` Dan Carpenter
2021-02-17  8:03 ` [PATCH v1 14/18] media: hantro: add G2 support to postproc Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03 ` [PATCH v1 15/18] media: hantro: handle V4L2_PIX_FMT_HEVC_SLICE control Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17 20:13   ` Ezequiel Garcia
2021-02-17 20:13     ` Ezequiel Garcia
2021-02-17 20:13     ` Ezequiel Garcia
2021-02-17 20:13     ` Ezequiel Garcia
2021-02-17  8:03 ` [PATCH v1 16/18] media: hantro: IMX8M: add variant for G2/HEVC codec Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03 ` [PATCH v1 17/18] dt-bindings: media: nxp,imx8mq-vpu: Update bindings Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17 22:48   ` Rob Herring
2021-02-17 22:48     ` Rob Herring
2021-02-17 22:48     ` Rob Herring
2021-02-17 22:48     ` Rob Herring
2021-02-18 14:48     ` Benjamin Gaignard
2021-02-18 14:48       ` Benjamin Gaignard
2021-02-18 14:48       ` Benjamin Gaignard
2021-02-18 14:48       ` Benjamin Gaignard
2021-02-17  8:03 ` [PATCH v1 18/18] arm64: dts: imx8mq: Add node to G2 hardware Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17  8:03   ` Benjamin Gaignard
2021-02-17 20:43   ` Ezequiel Garcia
2021-02-17 20:43     ` Ezequiel Garcia
2021-02-17 20:43     ` Ezequiel Garcia
2021-02-17 20:43     ` Ezequiel Garcia
2021-02-18 15:47     ` Benjamin Gaignard
2021-02-18 15:47       ` Benjamin Gaignard
2021-02-18 15:47       ` Benjamin Gaignard
2021-02-18 15:47       ` Benjamin Gaignard
2021-02-17  8:08 ` [PATCH v1 00/18] Add HANTRO G2/HEVC decoder support for IMX8MQ Greg KH
2021-02-17  8:08   ` Greg KH
2021-02-17  8:08   ` Greg KH
2021-02-17  8:08   ` Greg KH
2021-02-17  8:28   ` Benjamin Gaignard
2021-02-17  8:28     ` Benjamin Gaignard
2021-02-17  8:28     ` Benjamin Gaignard
2021-02-17  8:28     ` Benjamin Gaignard
2021-02-17  8:36     ` Greg KH
2021-02-17  8:36       ` Greg KH
2021-02-17  8:36       ` Greg KH
2021-02-17  8:36       ` Greg KH
2021-02-17  9:10       ` Hans Verkuil
2021-02-17  9:10         ` Hans Verkuil
2021-02-17  9:10         ` Hans Verkuil
2021-02-17  9:10         ` Hans Verkuil
2021-02-17  9:23         ` Greg KH
2021-02-17  9:23           ` Greg KH
2021-02-17  9:23           ` Greg KH
2021-02-17  9:23           ` Greg KH
2021-02-17  8:38     ` Paul Kocialkowski
2021-02-17  8:38       ` Paul Kocialkowski
2021-02-17  8:38       ` Paul Kocialkowski
2021-02-17  8:38       ` Paul Kocialkowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c029c980937ab50847bd0fcf86501e85bdb91fd3.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=Anson.Huang@nxp.com \
    --cc=adrian.ratiu@collabora.com \
    --cc=aisheng.dong@nxp.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel@collabora.com \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jernej.skrabec@siol.net \
    --cc=kernel@collabora.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mchehab@kernel.org \
    --cc=mripard@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=shengjiu.wang@nxp.com \
    --cc=wens@csie.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.