libcamera v0.7.2 Supporting cameras in Linux since 2019

Loading...
Searching...
No Matches
libcamera::controls::rpi Namespace Reference

Namespace for rpi controls. More...

## Enumerations
enum | { STATS_OUTPUT_ENABLE = 20001 , BCM2835_STATS_OUTPUT = 20002 , SCALER_CROPS = 20003 , PISP_STATS_OUTPUT = 20004 , SYNC_MODE = 20005 , SYNC_READY = 20006 , SYNC_TIMER = 20007 , SYNC_FRAMES = 20008 , CONTROL_LIST_SEQUENCE = 20009 }
enum | SyncModeEnum { SyncModeOff = 0 , SyncModeServer = 1 , SyncModeClient = 2 }
| Supported SyncMode values. More...

## Variables
const Control< bool > | StatsOutputEnable
| Toggles the Raspberry Pi IPA to output the hardware generated statistics.
const Control< Span< const uint8_t > > | Bcm2835StatsOutput
| Span of the BCM2835 ISP generated statistics for the current frame.
const Control< Span< const Rectangle > > | ScalerCrops
| An array of rectangles, where each singular value has identical functionality to the ScalerCrop control. This control allows the Raspberry Pi pipeline handler to control individual scaler crops per output stream.
const Control< Span< const uint8_t > > | PispStatsOutput
| Span of the PiSP Frontend ISP generated statistics for the current frame. This is sent in the Request metadata if the StatsOutputEnable is set to true. The statistics struct definition can be found in https://github.com/raspberrypi/libpisp/blob/main/src/libpisp/frontend/pisp_statistics.h.
const std::array< const ControlValue, 3 > | SyncModeValues
| List of all SyncMode supported values.
const std::map< std::string, int32_t > | SyncModeNameValueMap
| Map of all SyncMode supported value names (in std::string format) to value.
const Control< int32_t > | SyncMode
| Enable or disable camera synchronisation ("sync") mode.
const Control< bool > | SyncReady
| When using the camera synchronisation algorithm, the server broadcasts timing information to the clients. This also includes the time (some number of frames in the future, called the "ready time") at which the server will signal its controlling application, using this control, to start using the image frames.
const Control< int64_t > | SyncTimer
| This reports the amount of time, in microseconds, until the "ready time", at which the server and client will signal their controlling applications that the frames are now synchronised and should be used. The value may be refined slightly over time, becoming more precise as the "ready time" approaches.
const Control< int32_t > | SyncFrames
| The number of frames the server should wait, after enabling SyncModeServer, before signalling (via the SyncReady control) that frames should be used. This therefore determines the "ready time" for all synchronised cameras.
const Control< int64_t > | ControlListSequence
| This is the sequence number of the request whose control list has just been applied. Controls normally take several frames to apply, so the number here will refer to a request submitted a number of frames earlier.

## Detailed Description

Namespace for rpi controls.

## Enumeration Type Documentation

## ◆ SyncModeEnum

enum libcamera::controls::rpi::SyncModeEnum

Supported SyncMode values.

Enumerator
SyncModeOff | Disable sync mode.
SyncModeServer | Enable sync mode, act as server. The server broadcasts timing messages to any clients that are listening, so that the clients can synchronise their camera frames with the server's.
SyncModeClient | Enable sync mode, act as client. A client listens for any server messages, and arranges for its camera frames to synchronise as closely as possible with the server's. Many clients can listen out for the same server. Clients can also be started ahead of any servers, causing them merely to wait for the server to start.

## Variable Documentation

## ◆ Bcm2835StatsOutput

const Control<Span<const uint8_t> > libcamera::controls::rpi::Bcm2835StatsOutput
| extern

Span of the BCM2835 ISP generated statistics for the current frame.

This is sent in the Request metadata if the StatsOutputEnable is set to true. The statistics struct definition can be found in include/linux/bcm2835-isp.h.

See also
  StatsOutputEnable

## ◆ PispStatsOutput

const Control<Span<const uint8_t> > libcamera::controls::rpi::PispStatsOutput
| extern

Span of the PiSP Frontend ISP generated statistics for the current frame. This is sent in the Request metadata if the StatsOutputEnable is set to true. The statistics struct definition can be found in https://github.com/raspberrypi/libpisp/blob/main/src/libpisp/frontend/pisp_statistics.h.

See also
  StatsOutputEnable

## ◆ ScalerCrops

const Control<Span<const Rectangle> > libcamera::controls::rpi::ScalerCrops
| extern

An array of rectangles, where each singular value has identical functionality to the ScalerCrop control. This control allows the Raspberry Pi pipeline handler to control individual scaler crops per output stream.

The order of rectangles passed into the control must match the order of streams configured by the application. The pipeline handler will only configure crop retangles up-to the number of output streams configured. All subsequent rectangles passed into this control are ignored by the pipeline handler.

If both rpi::ScalerCrops and ScalerCrop controls are present in a ControlList, the latter is discarded, and crops are obtained from this control.

Note that using different crop rectangles for each output stream with this control is only applicable on the Pi5/PiSP platform. This control should also be considered temporary/draft and will be replaced with official libcamera API support for per-stream controls in the future.

See also
  ScalerCrop

## ◆ StatsOutputEnable

const Control<bool> libcamera::controls::rpi::StatsOutputEnable
| extern

Toggles the Raspberry Pi IPA to output the hardware generated statistics.

When this control is set to true, the IPA outputs a binary dump of the hardware generated statistics through the Request metadata in the Bcm2835StatsOutput control.

See also
  Bcm2835StatsOutput

## ◆ SyncFrames

const Control<int32_t> libcamera::controls::rpi::SyncFrames
| extern

The number of frames the server should wait, after enabling SyncModeServer, before signalling (via the SyncReady control) that frames should be used. This therefore determines the "ready time" for all synchronised cameras.

This control value should be set only for the device that is to act as the server, before or at the same moment at which SyncModeServer is enabled.

See also
  SyncMode
  SyncReady
  SyncTimer

## ◆ SyncMode

const Control<int32_t> libcamera::controls::rpi::SyncMode
| extern

Enable or disable camera synchronisation ("sync") mode.

When sync mode is enabled, a camera will synchronise frames temporally with other cameras, either attached to the same device or a different one. There should be one "server" device, which broadcasts timing information to one or more "clients". Communication is one-way, from server to clients only, and it is only clients that adjust their frame timings to match the server.

Sync mode requires all cameras to be running at (as far as possible) the same fixed framerate. Clients may continue to make adjustments to keep their cameras synchronised with the server for the duration of the session, though any updates after the initial ones should remain small.

See also
  SyncReady
  SyncTimer
  SyncFrames

## ◆ SyncReady

const Control<bool> libcamera::controls::rpi::SyncReady
| extern

When using the camera synchronisation algorithm, the server broadcasts timing information to the clients. This also includes the time (some number of frames in the future, called the "ready time") at which the server will signal its controlling application, using this control, to start using the image frames.

The client receives the "ready time" from the server, and will signal its application to start using the frames at this same moment.

While this control value is false, applications (on both client and server) should continue to wait, and not use the frames.

Once this value becomes true, it means that this is the first frame where the server and its clients have agreed that they will both be synchronised and that applications should begin consuming frames. Thereafter, this control will continue to signal the value true for the rest of the session.

See also
  SyncMode
  SyncTimer
  SyncFrames

## ◆ SyncTimer

const Control<int64_t> libcamera::controls::rpi::SyncTimer
| extern

This reports the amount of time, in microseconds, until the "ready time", at which the server and client will signal their controlling applications that the frames are now synchronised and should be used. The value may be refined slightly over time, becoming more precise as the "ready time" approaches.

Servers always report this value, whereas clients will omit this control until they have received a message from the server that enables them to calculate it.

Normally the value will start positive (the "ready time" is in the future), and decrease towards zero, before becoming negative (the "ready time" has elapsed). So there should be just one frame where the timer value is, or is very close to, zero - the one for which the SyncReady control becomes true. At this moment, the value indicates how closely synchronised the client believes it is with the server.

But note that if frames are being dropped, then the "near zero" valued frame, or indeed any other, could be skipped. In these cases the timer value allows an application to deduce that this has happened.

See also
  SyncMode
  SyncReady
  SyncFrames