Lines Matching refs:and

9    of connecting to a variety of systems and interfaces, typically uses i2c for
10    control and configuration, and a parallel or a serial bus for data.
12    specialised interface, present on many SoCs, e.g. PXA27x and PXA3xx, SuperH,
14  - camera host bus - a connection between a camera host and a camera. Can be
15    parallel or serial, consists of data and control lines, e.g. clock, vertical
16    and horizontal synchronization signals.
22 drivers and camera sensor drivers. Later the soc-camera sensor API has been
31 The subsystem has been designed to support multiple camera host interfaces and
40 omap1_camera.c, pxa_camera.c, sh_mobile_ceu_camera.c, and multiple sensor
74 .add and .remove methods are called when a sensor is attached to or detached
76 parameters between the host and the sensor. .init_videobuf2 is called by
81 .get_formats and, possibly, a .put_formats operations. See below for more
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
92 and can be obtained, using the soc_camera_i2c_to_link() macro. Care should be
93 taken, when using soc_camera_vdev_to_subdev() and when accessing struct
97 auxiliary soc-camera helper functions like soc_camera_power_on() and
98 soc_camera_power_off(), which switch regulators, provided by the platform and call
100 camera bus configuration capability flags and applies any board transformations,
103 soc_camera_limit_side() can be used to restrict beginning and length of a frame
106 VIDIOC_S_CROP and VIDIOC_S_FMT behaviour
111 VIDIOC_S_CROP: sets location and sizes of the sensor window. Unit is one sensor
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
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
125 driver may decide to also use its own scaling and cropping to fulfill the user's
128 Camera drivers are interfaced to the soc-camera core and to host drivers over
132 .s_fmt() and .try_fmt() have to be implemented too. Sensor window and scaling
140 User window geometry is kept in .user_width and .user_height fields in struct
141 soc_camera_device and used by the soc-camera core and host drivers. The core
149 V4L2 distinguishes between pixel formats, as they are stored in memory, and as
155 sample and stored in memory in the little-endian order with no gaps between
161 .get_formats and, if required, a .put_formats methods.