Lines Matching refs:camera

8  - camera / camera device / camera sensor - a video-camera sensor chip, capable
11  - camera host - an interface, to which a camera is connected. Typically a
14  - camera host bus - a connection between a camera host and a camera. Can be
18 Purpose of the soc-camera subsystem
21 The soc-camera subsystem initially provided a unified API between camera host
22 drivers and camera sensor drivers. Later the soc-camera sensor API has been
23 replaced with the V4L2 standard subdev API. This also made camera driver re-use
24 with non-soc-camera hosts possible. The camera host API to the soc-camera core
27 Soc-camera implements a V4L2 interface to the user, currently only the "mmap"
28 method is supported by host drivers. However, the soc-camera core also provides
31 The subsystem has been designed to support multiple camera host interfaces and
32 multiple cameras per interface, although most applications have only one camera
46 A host camera driver is registered using the
59 All camera host methods are passed in a struct soc_camera_host_ops:
77 soc-camera core when a video-device is opened, the host driver would typically
79 implemented completely by the specific camera host driver. If the host driver
89 platform, and used to specify to which camera host bus the sensor is connected,
90 and optionally provide platform .power and .reset methods for the camera. This
91 struct is provided to the camera driver via the I2C client device platform data
95 running on an soc-camera host. The actual camera driver operation is implemented
96 using the V4L2 subdev API. Additionally soc-camera camera drivers can use
97 auxiliary soc-camera helper functions like soc_camera_power_on() and
100 camera bus configuration capability flags and applies any board transformations,
104 side, based on camera capabilities.
119 In soc-camera there are two locations, where scaling and cropping can take
120 place: in the camera driver and in the host driver. User ioctls are first passed
121 to the host driver, which then generally passes them down to the camera driver.
122 It is more efficient to perform scaling and cropping in the camera driver to
123 save camera bus bandwidth and maximise the framerate. However, if the camera
128 Camera drivers are interfaced to the soc-camera core and to host drivers over
130 Therefore all camera drivers shall reply to .g_fmt() requests with their current
131 output geometry. This is necessary to correctly configure the camera bus.
133 factors have to be maintained by camera drivers internally. According to the
135 rely on camera drivers implementing .cropcap(). If the camera driver does not
137 cropping support by the camera host driver at least the .g_crop method must be
141 soc_camera_device and used by the soc-camera core and host drivers. The core
150 they are transferred over a media bus. Soc-camera provides support to
152 maintained by soc-camera core, which describes, what FOURCC pixel format will
157 standard transformations will be used by soc-camera or by camera host drivers to
158 configure camera drivers to produce the FOURCC format, requested by the user,