Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CSI2 drivers for RK35xx?

Featured Replies

I believe this question goes to @rpardini as maintainer of patches for Rockchip series in the `build` repo:

 

I'm trying connect camera to Orange Pi 3B (yes, it boots from community support on edge kernels), but spent 2h digging to find no drivers for CSI2 from Rockchip's fork are ported to patches for recent kernels (for example: https://github.com/armbian/linux-rockchip/blob/rk-5.10-rkr6/drivers/phy/rockchip/phy-rockchip-csi2-dphy.c and corresponding device trees to instantiate these drivers).

 

This is a little chicken egg problem as I need recent kernels to have access to open source GPU drivers - they're not present on 5.10 based original system images for OrangePi 3B.

 

I created a DT overlay for imx219 camera, but it cannot work as right references don't exist on Armbian yet.

 

I could help with porting these, but I need to know the procedure - that's some amount of drivers I can figure out based on `compatible = ` entries from Rockchip's device trees. I probably need to get them built with 6.6 and 6.7, then generate patches with these and PR changes. Any more hints appreciated.

I'm interested in having both MIPI CSI2 and GPU working on these boards for now:

  • OrangePi 3B (that one I have on my desk)
  • Radxa Zero 3E
  • Radxa Zero 3W

 

Thank you.

 

How you can live with forum not supporting humanly Markdown?

I think your real question is why hasn't Rockchip put in the effort to get these drivers into mainline linux?  It isn't the goal of Armbian to be the repository of large amounts of unmaintained code.  The goal is really to bring mainline linux to devices.  But that assumes that everyone else is working to bring various bits and pieces from custom linux forks to mainline linux.  While sometimes it is necessary to temporarily host code that has been ported to mainline, but not yet incorporated upstream, most of the efforts should be to get the code into upstream mainline linux.

 

  • Author
Quote

While sometimes it is necessary to temporarily host code that has been ported to mainline, but not yet incorporated upstream, most of the efforts should be to get the code into upstream mainline linux.

 

Whoa. I'm not representing Rockchip in anyway - just need to use RK3566 in a project. Without these drivers the support for the chip is incomplete from the perspective of the Armbian user. I don't have powers, energy and money to push particular chip drivers into mainline - there are several vendors our there who don't have theirs and Ubuntu still doing distros for these (👀 Xilinx/AMD).

 

Quote

It isn't the goal of Armbian to be the repository of large amounts of unmaintained code.

 

If that's the case what's the usefulness of Armbian for average tinkerer who want to run Rockchip based SBC with CSI-2 cameras? In Windows world you take the installer and add drivers to the system - in Linux world at best someone could cook DKMS package with extra set, but that's at the moment probably significantly more effort than set of patches for Armbian's build.
 

Quote

I think your real question is why hasn't Rockchip put in the effort to get these drivers into mainline linux?

 

Money, money, money. SBC makers doesn't pay them enough to justify effort required and they probably deliver customized kernels as part of paid support to they customers under NDAs. These things happen probably in violation of GPL license, but no one is willing to pay layers to chase this especially as 5.10 is out to the world.

 

Quote

It isn't the goal of Armbian to be the repository of large amounts of unmaintained code.

 

I don't have to PR my changes if you don't like such approach. That, however, doesn't change my need to do this as I need to boot the board with CSI-2 support and working GPU 🤷

Greetings.

@Michal Fita - tell me please, did you manage to port csi2 drivers to the mainline kernel? I am also very interested in the camera operation on RK3566.

 

Edited by adron

35 minutes ago, adron said:

my GC02M2 camera is a RAW sensor ➝ needs RK3566 ISP driver for usable output.

Then you know which part you can contribute to mainline support, otherwise you have to use the manufacturer's BSP, because that's what you paid for.

BSP kernel is good, of course. The only thing that confuses me is the lack of upgrading to mainline branch 6.1. The latest version of mainline is 6.1.147. And Armbian still uses 6.1.115.

Hello! Is there any progress? I need to grab raw CSI2 camera on kernel 6.12 but Armbian has no CSI2-ISP stack at all at this kernel. I try to port CSI2-phy, ISP and CIF drivers from 6.1, fix compile errors, add DTS bindings but have to lack yet (need to learn new v4l2 media framework).

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.