All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: linkmauve@linkmauve.fr
Cc: andy.yan@rock-chips.com, conor+dt@kernel.org,
	cristian.ciocaltea@collabora.com, devicetree@vger.kernel.org,
	dsimic@manjaro.org, ezequiel@vanguardiasur.com.ar,
	frattaroli.nicolas@gmail.com, heiko@sntech.de,
	iommu@lists.linux.dev, joro@8bytes.org,
	krzysztof.kozlowski+dt@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-rockchip@lists.infradead.org, macromorgan@hotmail.com,
	mchehab@kernel.org, p.zabel@pengutronix.de, robh@kernel.org,
	robin.murphy@arm.com, sebastian.reichel@collabora.com,
	shreeya.patel@collabora.com, will@kernel.org, sigmaris@gmail.com,
	nicolas@ndufresne.ca
Subject: Re: [PATCH v4 0/2] Enable JPEG encoding on rk3588
Date: Sat, 27 Apr 2024 15:16:38 +0800	[thread overview]
Message-ID: <20240427071638.79915-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <20240418141509.2485053-1-linkmauve@linkmauve.fr>

Hi Emmanuel,

On Thu, 18 Apr 2024 16:15:04 +0200, Emmanuel Gil Peyrot wrote:
>- Only expose a single VEPU121, since the driver doesn’t yet support
>  exposing them all as a single video node to userspace.
I'm also doing work with the hantro node on rk3588 which has both vdpu
and vepu. Discussions can be found here[1]. If I enable the jpeg encoder
at feb50000, would it cause any side effects if other jpeg encoders in
your patch are enabled? And what's the disadvantage of enabling multi
jpeg endoers in devicetree?

[1] https://patchwork.kernel.org/project/linux-rockchip/patch/20240418111002.83015-3-liujianfeng1994@gmail.com/

Best regards,
Jianfeng

WARNING: multiple messages have this Message-ID (diff)
From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: linkmauve@linkmauve.fr
Cc: andy.yan@rock-chips.com, conor+dt@kernel.org,
	cristian.ciocaltea@collabora.com, devicetree@vger.kernel.org,
	dsimic@manjaro.org, ezequiel@vanguardiasur.com.ar,
	frattaroli.nicolas@gmail.com, heiko@sntech.de,
	iommu@lists.linux.dev, joro@8bytes.org,
	krzysztof.kozlowski+dt@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-rockchip@lists.infradead.org, macromorgan@hotmail.com,
	mchehab@kernel.org, p.zabel@pengutronix.de, robh@kernel.org,
	robin.murphy@arm.com, sebastian.reichel@collabora.com,
	shreeya.patel@collabora.com, will@kernel.org, sigmaris@gmail.com,
	nicolas@ndufresne.ca
Subject: Re: [PATCH v4 0/2] Enable JPEG encoding on rk3588
Date: Sat, 27 Apr 2024 15:16:38 +0800	[thread overview]
Message-ID: <20240427071638.79915-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <20240418141509.2485053-1-linkmauve@linkmauve.fr>

Hi Emmanuel,

On Thu, 18 Apr 2024 16:15:04 +0200, Emmanuel Gil Peyrot wrote:
>- Only expose a single VEPU121, since the driver doesn’t yet support
>  exposing them all as a single video node to userspace.
I'm also doing work with the hantro node on rk3588 which has both vdpu
and vepu. Discussions can be found here[1]. If I enable the jpeg encoder
at feb50000, would it cause any side effects if other jpeg encoders in
your patch are enabled? And what's the disadvantage of enabling multi
jpeg endoers in devicetree?

[1] https://patchwork.kernel.org/project/linux-rockchip/patch/20240418111002.83015-3-liujianfeng1994@gmail.com/

Best regards,
Jianfeng

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

WARNING: multiple messages have this Message-ID (diff)
From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: linkmauve@linkmauve.fr
Cc: andy.yan@rock-chips.com, conor+dt@kernel.org,
	cristian.ciocaltea@collabora.com, devicetree@vger.kernel.org,
	dsimic@manjaro.org, ezequiel@vanguardiasur.com.ar,
	frattaroli.nicolas@gmail.com, heiko@sntech.de,
	iommu@lists.linux.dev, joro@8bytes.org,
	krzysztof.kozlowski+dt@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-rockchip@lists.infradead.org, macromorgan@hotmail.com,
	mchehab@kernel.org, p.zabel@pengutronix.de, robh@kernel.org,
	robin.murphy@arm.com, sebastian.reichel@collabora.com,
	shreeya.patel@collabora.com, will@kernel.org, sigmaris@gmail.com,
	nicolas@ndufresne.ca
Subject: Re: [PATCH v4 0/2] Enable JPEG encoding on rk3588
Date: Sat, 27 Apr 2024 15:16:38 +0800	[thread overview]
Message-ID: <20240427071638.79915-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <20240418141509.2485053-1-linkmauve@linkmauve.fr>

Hi Emmanuel,

On Thu, 18 Apr 2024 16:15:04 +0200, Emmanuel Gil Peyrot wrote:
>- Only expose a single VEPU121, since the driver doesn’t yet support
>  exposing them all as a single video node to userspace.
I'm also doing work with the hantro node on rk3588 which has both vdpu
and vepu. Discussions can be found here[1]. If I enable the jpeg encoder
at feb50000, would it cause any side effects if other jpeg encoders in
your patch are enabled? And what's the disadvantage of enabling multi
jpeg endoers in devicetree?

[1] https://patchwork.kernel.org/project/linux-rockchip/patch/20240418111002.83015-3-liujianfeng1994@gmail.com/

Best regards,
Jianfeng

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

  parent reply	other threads:[~2024-04-27  7:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 14:15 [PATCH v4 0/2] Enable JPEG encoding on rk3588 Emmanuel Gil Peyrot
2024-04-18 14:15 ` Emmanuel Gil Peyrot
2024-04-18 14:15 ` Emmanuel Gil Peyrot
2024-04-18 14:15 ` [PATCH v4 1/2] media: dt-binding: Document rk3588’s VEPU121 Emmanuel Gil Peyrot
2024-04-18 14:15   ` Emmanuel Gil Peyrot
2024-04-18 14:15   ` Emmanuel Gil Peyrot
2024-04-18 14:15 ` [PATCH v4 2/2] arm64: dts: rockchip: Add one VEPU121 to rk3588 Emmanuel Gil Peyrot
2024-04-18 14:15   ` Emmanuel Gil Peyrot
2024-04-18 14:15   ` Emmanuel Gil Peyrot
2024-04-27  7:16 ` Jianfeng Liu [this message]
2024-04-27  7:16   ` [PATCH v4 0/2] Enable JPEG encoding on rk3588 Jianfeng Liu
2024-04-27  7:16   ` Jianfeng Liu
2024-04-28 17:01   ` Heiko Stübner
2024-04-28 17:01     ` Heiko Stübner
2024-04-28 17:01     ` Heiko Stübner
2024-04-28 17:29     ` Jianfeng Liu
2024-04-28 17:29       ` Jianfeng Liu
2024-04-28 17:29       ` Jianfeng Liu

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=20240427071638.79915-1-liujianfeng1994@gmail.com \
    --to=liujianfeng1994@gmail.com \
    --cc=andy.yan@rock-chips.com \
    --cc=conor+dt@kernel.org \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=frattaroli.nicolas@gmail.com \
    --cc=heiko@sntech.de \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linkmauve@linkmauve.fr \
    --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=macromorgan@hotmail.com \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=sebastian.reichel@collabora.com \
    --cc=shreeya.patel@collabora.com \
    --cc=sigmaris@gmail.com \
    --cc=will@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.