public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Riesch <michael.riesch@wolfvision.net>
To: Yogesh Hegde <yogi.kernel@gmail.com>,
	Dafna Hirschfeld <dafna@fastmail.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	linux-rockchip@lists.infradead.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: skhan@linuxfoundation.org, ivan.orlov0322@gmail.com,
	kernelnewbies@kernelnewbies.org
Subject: Re: Seeking guidance for Adding ISP Driver for RK3568
Date: Tue, 11 Jul 2023 11:29:34 +0200	[thread overview]
Message-ID: <85ffc0b2-efbb-5d70-ab75-e3e9f0c74bf9@wolfvision.net> (raw)
In-Reply-To: <ZK0ApOXkmkSO98kM@zephyrusG14>

Hi Yogesh,

Cc: Laurent as I had a chat with him about 1.

On 7/11/23 09:11, Yogesh Hegde wrote:
> 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 ?

That's a very good question, but unfortunately there is no clear answer
to it. We were able to hack the existing mainline rkisp1 driver so that
it works with the RK3568 ISP (rkisp v2.1), but the result is far from
being mainline material.

I would say that there is enough overlap that the RK3568 ISP code should
enter drivers/media/platform/rockchip/rkisp1/ but on the other hand the
differences are so significant that there should be separate
rkisp2-{csi,params,...}.c files.

Example for overlap: With some refactoring applied, rkisp1-capture.c
could support the RK3568 ISP as well.

Example for significant changes: the CSI subdevice is fundamentally
different, so most likely there will be a rkisp2-csi.c.

Example for a mixture of both: a new stats/params interface to user
space will be required for the RK3568 ISP, but if this is designed to be
general enough, it might be reused for the older ISP versions at some point.

> 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?

I think the tendency is towards skipping staging, but I don't have a say
on that one.

> 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?

Downstream code is GPL'ed, so it should be fine.

> 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.

Cool! Just be aware that you picked a complex beast for your first full
driver.

> 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.

What camera sensor hardware do you have?

Best regards,
Michael

> 
> 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

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

  reply	other threads:[~2023-07-11  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  7:11 Seeking guidance for Adding ISP Driver for RK3568 Yogesh Hegde
2023-07-11  9:29 ` Michael Riesch [this message]
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=85ffc0b2-efbb-5d70-ab75-e3e9f0c74bf9@wolfvision.net \
    --to=michael.riesch@wolfvision.net \
    --cc=dafna@fastmail.com \
    --cc=heiko@sntech.de \
    --cc=ivan.orlov0322@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mchehab@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=yogi.kernel@gmail.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