Tags: kimocoder/rpi-linux
Tags
configs: Really enable Hailo accelerator driver For real, this time.
dts: bcm2712: cm5: Force the ANT pins to GPIOs The magic required to make requesting a GPIO automatically change the pinmux settings is currently absent. Work around that by explicitly requesting that the ANT pins be in GPIO mode. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
drm/vc4: Fix atomic_async_check to call the right mode_set function vc4_plane_atomic_async_check was always calling vc4_plane_mode_set to validate and generate the dlist for the check. If async_check decided it had to fall back to a sync commit, then this GEN4/5 dlist could get used on GEN6. Call either vc4_plane_mode_set or vc6_plane_mode_set as appropriate. Fixes: 1ab1fbb ("drm/vc4: hvs: Support BCM2712 HVS") Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
drm: vc4: Block swiotlb bounce buffers being imported as dmabuf The dmabuf import already checks that the backing buffer is contiguous and rejects it if it isn't. vc4 also requires that the buffer is in the bottom 1GB of RAM, and this is all correctly defined via dma-ranges. However the kernel silently uses swiotlb to bounce dma buffers around if they are in the wrong region. This relies on dma sync functions to be called in order to copy the data to/from the bounce buffer. DRM is based on all memory allocations being coherent with the GPU so that any updates to a framebuffer will be acted on without the need for any additional update. This is fairly fundamentally incompatible with needing to call dma_sync_ to handle the bounce buffer copies, and therefore we have to detect and reject mappings that use bounce buffers. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
drivers: media: imx477: Set horizontal binning when disabling the scaler The horizontal scaler has been disabled but actually the sensor is not binning horizontally, resulting in images that are stretched 2x horizontally (missing the right half of the field of view completely). Therefore we must additionally set the horizontal binning mode. There is only marginal change in output quality and noise levels. Signed-off-by: David Plowman <david.plowman@raspberrypi.com> Fixes: f075893 ("drivers: media: imx477: Disable the scaler")
fixup! overlays: mcp23017: allow specification of the i2c bus The incorrect fragment order (*) caused broke the interrupt usage, and while it was being fixed the lack of a reference to the pinctrl declaration was noticed. See: raspberrypi#5677 Signed-off-by: Phil Elwell <phil@raspberrypi.com> (*) Ideally all fragments would appear in the file in the order in which they should be merged, but that is easy to forget and can be awkward, so the firmware merges all "intra" fragments (those that target other fragments in the overlay) before "inter" fragments (those that target the base DTB). However, intra fragments that target other intra fragments is a level of nesting too far for this logic to cope, so they must appear before the fragments they target.
vc4/drm: Remove the clear of SCALER_DISPBKGND_FILL Since "drm/vc4: hvs: Support BCM2712 HVS" booting Pi4 with dual 4kp30 displays connected fails with: vc4-drm gpu: [drm] *ERROR* [CRTC:107:pixelvalve-4] flip_done timed out It has been tracked down to the referenced commit adding a path to clear the SCALER_DISPBKGND_FILL when not required. Dual 4kp30 works with a core clock of 297MHz when background fill is enabled, but requires a higher value with it disabled. 320MHz still fails, while 330MHz seems okay. Lets always enable background fill for Pi0-4. Fixes: e84da23 ("drm/vc4: hvs: Support BCM2712 HVS") Signed-off-by: Dom Cobley <popcornmix@gmail.com>
fixup! gpio-fsm: Avoid truncation of delay jiffies The kernel's time unit of jiffies should be stored as an unsigned long value. Storing it as an unsigned int, as gpio-fsm did, leads to truncation and malfunction when the kernel is built for a 64-bit platform. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
media: imx219: Advertise embedded data node on media pad 1 This commit updates the imx219 driver to adverise support for embedded data streams. This can then be used by the bcm2835-unicam driver, which has recently been updated to expose the embedded data stream to userland. The imx219 sensor subdevice overloads the media pad to differentiate between image stream (pad 0) and embedded data stream (pad 1) when performing the v4l2_subdev_pad_ops functions. Signed-off-by: Naushir Patuck <naush@raspberrypi.com> Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
imx708: Do not reset vblank to a default value imx708_set_framing_limits resets the vblank control to the mode default value unconditionally. This causes it to overwrite the user specified vblank and exposure control values when starting the sensor, since it is called when handling V4L2_CID_WIDE_DYNAMIC_RANGE. Remove this call to s_ctrl as it is unnecessary. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
PreviousNext