From: Suniel Mahesh <suniel.spartan@gmail.com>
To: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Hans Verkuil <hansverk@cisco.com>,
Jacob Chen <jacob-chen@iotwrt.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Ezequiel Garcia <ezequiel@collabora.com>
Subject: [PATCH 0/4] media: rockchip: rga: PX30 support and YUV2YUV fix
Date: Tue, 11 Jan 2022 13:52:34 +0530 [thread overview]
Message-ID: <9e7aa8de-30cf-e3e0-4c5f-e4b989ea8b48@gmail.com> (raw)
Hi Paul/All,
I have added this patch series onto linux-next and testing RGA on PX30.
Log Snippet:
root@px30-engicam-px30-core-ctouch2:/# dmesg | grep rga
rockchip-rga ff480000.rga: HW Version: 0x04.00
rockchip-rga ff480000.rga: Registered rockchip-rga as /dev/video0
How do I test this ? In the email you mentioned:
I tested it with a standalone utility setting V4L2_PIX_FMT_YUV420 on
both output and capture. The issue should be pretty easy to reproduce.
Can you please share more information/any procedure on how to test.
Thanks and Regards
Suniel Mahesh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-01-11 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 8:22 Suniel Mahesh [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-16 11:50 [PATCH 0/4] media: rockchip: rga: PX30 support and YUV2YUV fix Paul Kocialkowski
2020-04-16 12:22 ` Ezequiel Garcia
2020-04-16 12: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=9e7aa8de-30cf-e3e0-4c5f-e4b989ea8b48@gmail.com \
--to=suniel.spartan@gmail.com \
--cc=20200416115047.233720-1-paul.kocialkowski@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=hansverk@cisco.com \
--cc=heiko@sntech.de \
--cc=jacob-chen@iotwrt.com \
--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=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=paul.kocialkowski@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).