From: Yogesh Hegde <yogi.kernel@gmail.com>
To: Dafna Hirschfeld <dafna@fastmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org
Cc: skhan@linuxfoundation.org, ivan.orlov0322@gmail.com,
kernelnewbies@kernelnewbies.org
Subject: Seeking guidance for Adding ISP Driver for RK3568
Date: Tue, 11 Jul 2023 12:41:32 +0530 [thread overview]
Message-ID: <ZK0ApOXkmkSO98kM@zephyrusG14> (raw)
Hi,
I am seeking your expert guidance and assistance in adding the ISP driver for
RK3568 to the Linux Kernel.
Before I start, I have a few questions regarding the process of
adding the ISP driver for RK3568 and upstreaming it to the Linux Kernel.
I greatly appreciate any insights you can provide on the following points:
1. Integration with existing RK3399 ISP driver: Since the ISP driver for RK3399
has already been upstreamed, I would like to understand if the ISP driver
for RK3568 will be added to the existing RK3399 ISP driver or if it will be
a completely new driver ?
2. Upstreaming process and staging: I would like to know if the upstreaming
process for the RK3568 ISP driver will involve starting with the downstream
driver and adding it to the staging area. From there, would it be merged
into the media subsystem or follow a different process altogether?
3. Permission requirements from Rockchip: To ensure a smooth upstreaming
process, I would like to know if I need any permissions or approvals from
Rockchip, the manufacturer of the RK3568 chipset. If permissions are
required, could you please guide me on how to obtain them?
I would also like to mention that while this is my first time upstreaming a
full driver, I do have some experience working with the media subsystem.
I am willing to devote the necessary time and effort to learn and contribute
effectively to the upstreaming process also I have Rock 3A development board,
which will be helpful in testing the ISP driver.
Thank you very much for considering my request. I eagerly await your responses
and any direction you and the mailing list members can provide.
Thanks & Regards,
Yogesh
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2023-07-11 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 7:11 Yogesh Hegde [this message]
2023-07-11 9:29 ` Seeking guidance for Adding ISP Driver for RK3568 Michael Riesch
2023-07-12 7:07 ` Yogesh Hegde
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=ZK0ApOXkmkSO98kM@zephyrusG14 \
--to=yogi.kernel@gmail.com \
--cc=dafna@fastmail.com \
--cc=heiko@sntech.de \
--cc=ivan.orlov0322@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox