All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	 Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter Geis <pgwipeout@gmail.com>,
	Michael Riesch <michael.riesch@wolfvision.net>,
	Liang Chen <cl@rock-chips.com>
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
	 devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH 0/3] Enable JPEG Encoder on RK3566/RK3568
Date: Fri, 29 Apr 2022 10:46:01 -0400	[thread overview]
Message-ID: <198ce3981ad15844627581f9519cab67ed2a81c1.camel@ndufresne.ca> (raw)
In-Reply-To: <20220427224438.335327-1-frattaroli.nicolas@gmail.com>

Le jeudi 28 avril 2022 à 00:44 +0200, Nicolas Frattaroli a écrit :
> Hello,
> 
> the following series adds support for and enables the hardware JPEG
> encoder on the RK3566 and RK3568 line of SoCs by Rockchip.
> 
> The JPEG encoder is its own little Hantro instance with seemingly just
> the encode functionality.

I'm a little suspicious about this statement. I believe the Hantro combo is
identical to RK3399 and that you are confusing with Rockchip JPEG encoder here.
Here's the source of my suspicion:

https://github.com/JeffyCN/rockchip_mirrors/blob/mpp/osal/mpp_soc.cpp#L637

As this get burnt into DT, we really need to get this right. Perhaps we need to
run the reference software to verify ? Ping me if you need help with that.

> 
> The first patch modifies the bindings with a new compatible, and adds
> the ability to just have a vepu interrupt without a vdpu interrupt.
> 
> The second patch makes the actual driver changes to support this variant.
> 
> The third and final patch makes the necessary device tree changes for
> the rk356x device tree file to add both the node for the encoder and
> its MMU.
> 
> The series has been tested on a PINE64 Quartz64 Model A with an RK3566
> SoC using GStreamer.
> 
> Regards,
> Nicolas Frattaroli
> 
> Nicolas Frattaroli (3):
>   dt-bindings: media: rockchip-vpu: Add RK3568 JPEG compatible
>   media: hantro: Add support for RK356x JPEG encoder
>   arm64: dts: rockchip: Add JPEG encoder node to rk356x
> 
>  .../bindings/media/rockchip-vpu.yaml          |  2 +
>  arch/arm64/boot/dts/rockchip/rk356x.dtsi      | 21 +++++++
>  drivers/staging/media/hantro/hantro_drv.c     |  1 +
>  drivers/staging/media/hantro/hantro_hw.h      |  1 +
>  .../staging/media/hantro/rockchip_vpu_hw.c    | 62 +++++++++++++++++++
>  5 files changed, 87 insertions(+)
> 


WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	 Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter Geis <pgwipeout@gmail.com>,
	Michael Riesch <michael.riesch@wolfvision.net>,
	Liang Chen <cl@rock-chips.com>
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
	 devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH 0/3] Enable JPEG Encoder on RK3566/RK3568
Date: Fri, 29 Apr 2022 10:46:01 -0400	[thread overview]
Message-ID: <198ce3981ad15844627581f9519cab67ed2a81c1.camel@ndufresne.ca> (raw)
In-Reply-To: <20220427224438.335327-1-frattaroli.nicolas@gmail.com>

Le jeudi 28 avril 2022 à 00:44 +0200, Nicolas Frattaroli a écrit :
> Hello,
> 
> the following series adds support for and enables the hardware JPEG
> encoder on the RK3566 and RK3568 line of SoCs by Rockchip.
> 
> The JPEG encoder is its own little Hantro instance with seemingly just
> the encode functionality.

I'm a little suspicious about this statement. I believe the Hantro combo is
identical to RK3399 and that you are confusing with Rockchip JPEG encoder here.
Here's the source of my suspicion:

https://github.com/JeffyCN/rockchip_mirrors/blob/mpp/osal/mpp_soc.cpp#L637

As this get burnt into DT, we really need to get this right. Perhaps we need to
run the reference software to verify ? Ping me if you need help with that.

> 
> The first patch modifies the bindings with a new compatible, and adds
> the ability to just have a vepu interrupt without a vdpu interrupt.
> 
> The second patch makes the actual driver changes to support this variant.
> 
> The third and final patch makes the necessary device tree changes for
> the rk356x device tree file to add both the node for the encoder and
> its MMU.
> 
> The series has been tested on a PINE64 Quartz64 Model A with an RK3566
> SoC using GStreamer.
> 
> Regards,
> Nicolas Frattaroli
> 
> Nicolas Frattaroli (3):
>   dt-bindings: media: rockchip-vpu: Add RK3568 JPEG compatible
>   media: hantro: Add support for RK356x JPEG encoder
>   arm64: dts: rockchip: Add JPEG encoder node to rk356x
> 
>  .../bindings/media/rockchip-vpu.yaml          |  2 +
>  arch/arm64/boot/dts/rockchip/rk356x.dtsi      | 21 +++++++
>  drivers/staging/media/hantro/hantro_drv.c     |  1 +
>  drivers/staging/media/hantro/hantro_hw.h      |  1 +
>  .../staging/media/hantro/rockchip_vpu_hw.c    | 62 +++++++++++++++++++
>  5 files changed, 87 insertions(+)
> 


_______________________________________________
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: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	 Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter Geis <pgwipeout@gmail.com>,
	Michael Riesch <michael.riesch@wolfvision.net>,
	Liang Chen <cl@rock-chips.com>
Cc: linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
	 devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH 0/3] Enable JPEG Encoder on RK3566/RK3568
Date: Fri, 29 Apr 2022 10:46:01 -0400	[thread overview]
Message-ID: <198ce3981ad15844627581f9519cab67ed2a81c1.camel@ndufresne.ca> (raw)
In-Reply-To: <20220427224438.335327-1-frattaroli.nicolas@gmail.com>

Le jeudi 28 avril 2022 à 00:44 +0200, Nicolas Frattaroli a écrit :
> Hello,
> 
> the following series adds support for and enables the hardware JPEG
> encoder on the RK3566 and RK3568 line of SoCs by Rockchip.
> 
> The JPEG encoder is its own little Hantro instance with seemingly just
> the encode functionality.

I'm a little suspicious about this statement. I believe the Hantro combo is
identical to RK3399 and that you are confusing with Rockchip JPEG encoder here.
Here's the source of my suspicion:

https://github.com/JeffyCN/rockchip_mirrors/blob/mpp/osal/mpp_soc.cpp#L637

As this get burnt into DT, we really need to get this right. Perhaps we need to
run the reference software to verify ? Ping me if you need help with that.

> 
> The first patch modifies the bindings with a new compatible, and adds
> the ability to just have a vepu interrupt without a vdpu interrupt.
> 
> The second patch makes the actual driver changes to support this variant.
> 
> The third and final patch makes the necessary device tree changes for
> the rk356x device tree file to add both the node for the encoder and
> its MMU.
> 
> The series has been tested on a PINE64 Quartz64 Model A with an RK3566
> SoC using GStreamer.
> 
> Regards,
> Nicolas Frattaroli
> 
> Nicolas Frattaroli (3):
>   dt-bindings: media: rockchip-vpu: Add RK3568 JPEG compatible
>   media: hantro: Add support for RK356x JPEG encoder
>   arm64: dts: rockchip: Add JPEG encoder node to rk356x
> 
>  .../bindings/media/rockchip-vpu.yaml          |  2 +
>  arch/arm64/boot/dts/rockchip/rk356x.dtsi      | 21 +++++++
>  drivers/staging/media/hantro/hantro_drv.c     |  1 +
>  drivers/staging/media/hantro/hantro_hw.h      |  1 +
>  .../staging/media/hantro/rockchip_vpu_hw.c    | 62 +++++++++++++++++++
>  5 files changed, 87 insertions(+)
> 


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

  parent reply	other threads:[~2022-04-29 14:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 22:44 [PATCH 0/3] Enable JPEG Encoder on RK3566/RK3568 Nicolas Frattaroli
2022-04-27 22:44 ` Nicolas Frattaroli
2022-04-27 22:44 ` Nicolas Frattaroli
2022-04-27 22:44 ` [PATCH 1/3] dt-bindings: media: rockchip-vpu: Add RK3568 JPEG compatible Nicolas Frattaroli
2022-04-27 22:44   ` Nicolas Frattaroli
2022-04-27 22:44   ` Nicolas Frattaroli
2022-05-04 20:23   ` Rob Herring
2022-05-04 20:23     ` Rob Herring
2022-05-04 20:23     ` Rob Herring
2022-04-27 22:44 ` [PATCH 2/3] media: hantro: Add support for RK356x JPEG encoder Nicolas Frattaroli
2022-04-27 22:44   ` Nicolas Frattaroli
2022-04-27 22:44   ` Nicolas Frattaroli
2022-08-09 12:45   ` Michael Grzeschik
2022-08-09 12:45     ` Michael Grzeschik
2022-08-09 12:45     ` Michael Grzeschik
2022-08-09 18:43     ` Michael Grzeschik
2022-08-09 18:43       ` Michael Grzeschik
2022-08-09 18:43       ` Michael Grzeschik
2022-04-27 22:44 ` [PATCH 3/3] arm64: dts: rockchip: Add JPEG encoder node to rk356x Nicolas Frattaroli
2022-04-27 22:44   ` Nicolas Frattaroli
2022-04-27 22:44   ` Nicolas Frattaroli
2022-04-29 14:46 ` Nicolas Dufresne [this message]
2022-04-29 14:46   ` [PATCH 0/3] Enable JPEG Encoder on RK3566/RK3568 Nicolas Dufresne
2022-04-29 14:46   ` Nicolas Dufresne
2022-04-29 15:28   ` Nicolas Frattaroli
2022-04-29 15:28     ` Nicolas Frattaroli
2022-04-29 15:28     ` Nicolas Frattaroli
2022-04-29 23:20     ` Michael Grzeschik
2022-04-29 23:20       ` Michael Grzeschik
2022-04-29 23:20       ` Michael Grzeschik
2022-05-02 12:20       ` Nicolas Dufresne
2022-05-02 12:20         ` Nicolas Dufresne
2022-05-02 12:20         ` Nicolas Dufresne
2022-06-20 13:40         ` Michael Grzeschik
2022-06-20 13:40           ` Michael Grzeschik
2022-06-20 13:40           ` Michael Grzeschik
2022-06-21 14:44           ` Nicolas Dufresne
2022-06-21 14:44             ` Nicolas Dufresne
2022-06-21 14:44             ` Nicolas Dufresne

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=198ce3981ad15844627581f9519cab67ed2a81c1.camel@ndufresne.ca \
    --to=nicolas@ndufresne.ca \
    --cc=cl@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=frattaroli.nicolas@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=michael.riesch@wolfvision.net \
    --cc=p.zabel@pengutronix.de \
    --cc=pgwipeout@gmail.com \
    --cc=robh+dt@kernel.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.