- Jan 08, 2021
-
-
Dave Stevenson authored
Control V4L2_CID_MPEG_VIDEO_HEADER_MODE controls whether the encoder is meant to emit the header bytes as a separate packet or with the first encoded frame. Add support for it. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Naushir Patuck authored
To comply with the intended usage of the V4L2 selection target when used to retrieve a sensor image properties, adjust the rectangles returned by the imx477 driver. The top/left crop coordinates of the TGT_CROP rectangle were set to (0, 0) instead of (8, 16) which is the offset from the larger physical pixel array rectangle. This was also a mismatch with the default values crop rectangle value, so this is corrected. Found with v4l2-compliance. While at it, add V4L2_SEL_TGT_CROP_BOUNDS support: CROP_DEFAULT and CROP_BOUNDS have the same size as the non-active pixels are not readable using the selection API. Found with v4l2-compliance. This commit mirrors 543790f7 done for the imx219 sensor. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Phil Elwell authored
The overlays for the ads1015 and ads1115 I2C ADCs omitted the addresses in the main device node names. As well as breaking the conventions for I2C devices, this prevents the firmware from renaming them when the "reg" property is modified, which in turn stops the overlays from being instantiated multiple times. See: https://www.raspberrypi.org/forums/viewtopic.php?f=107&t=294465 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Dom Cobley authored
Eric's view was that there was no point in having zpos support on vc4 as all the planes had the same functionality. Can be later squashed into (and fixes): drm/vc4: Add firmware-kms mode Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Phil Elwell authored
The mpu6050 starts up at address 0x68 by default, but can be set to 0x69 if the ADO pin is pulled high. Give the overlay an addr parameter to allow devices at the alternate address to be used. See: https://github.com/Hexxeh/rpi-firmware/issues/252 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
lan78xx_link_reset explicitly clears the MAC's view of the PHY's IRQ status. In doing so it potentially leaves the PHY with a pending interrupt that will never be acknowledged, at which point no further interrupts will be generated. Avoid the problem by acknowledging any pending PHY interrupt after clearing the MAC's status bit. See: https://github.com/raspberrypi/linux/issues/2937 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Naushir Patuck authored
This reverts commit 961d3b27. The updated length check for dmabuf types broke existing usage in v4l2 userland clients. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Dave Stevenson authored
The firmware by default tries to ensure that decoded frame timestamps always increment. This is counter to the V4L2 API which wants exactly the OUTPUT queue timestamps passed to the CAPTURE queue buffers. Disable the firmware option. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Phil Elwell authored
Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
Add support for the PCF85063 and PCF85063A RTC devices to the i2c-rtc overlay. Also enable the device to be used on i2c0 (i2c_vc) on GPIOs 0&1 (use parameter "i2c0") and GPIOs 44 & 45 (use parameter "i2c_csi_dsi"). Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
Include the driver module for the PCF85063 and PCF85063A RTC devices. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
Although the BRCMSTB PCIe interface doesn't technically support the MSI-X spec, in practise it seems to work provided no more than 32 MSI-Xs are required. Add the required flag to the driver to allow experimentation with devices that demand MSI-X support. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Naushir Patuck authored
Commit 65e08c465020d4c5b51afb452efc2246d80fd66f failed to clear the clock state when the device stopped streaming. Fix this, as it might again cause the same problems when doing an unprepare. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Naushir Patuck authored
clk_disable_unprepare() is called unconditionally in stop_streaming(). This is incorrect in the cases where start_streaming() fails, and unprepares all clocks as part of the failure cleanup. To avoid this, ensure that clk_disable_unprepare() is only called in stop_streaming() if the clocks are in a prepared state. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Naushir Patuck authored
On a failure in start_streaming(), the error code would not propagate to the calling function on all conditions. This would cause the userland caller to not know of the failure. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
paul-1 authored
Create unique names for the two instances of the codec driver. Signed-off-by: Paul Hermann <paul@picoreplayer.org>
-
Sudeep authored
Signed-off-by: Sudeep <sudeepkumar@cem-solutions.net>
-
Sudeep authored
Signed-off-by: Sudeep <sudeepkumar@cem-solutions.net>
-
Sudeep authored
Signed-off-by: Sudeep <sudeepkumar@cem-solutions.net>
-
Dave Stevenson authored
The DSI1_PHY_AFEC0_PD_DLANE1 and DSI1_PHY_AFEC0_PD_DLANE3 register definitions were swapped, so trying to use more than a single data lane failed as lane 1 would get powered down. (In theory a 4 lane device would work as all lanes would remain powered). Correct the definitions. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dom Cobley authored
The hdmi reset got moved to a later point in "drm/vc4: hdmi: Add reset callback" which now occurs after vc4_hdmi_cec_init and so tramples the setup of registers like HDMI_CEC_CNTRL_1 This only affects pi0-3 as on pi4 the cec resgisters are in a separate block Fixes: ed9a1f6eb4402b25b8a983dc4bfe40f025176e03 Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Dave Stevenson authored
Updates the compatible string for DSI1 on BCM2711 to differentiate it from BCM2835. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
BCM2711 DSI1 doesn't have the issue with the ARM not being able to write to the registers, therefore remove the DMA workaround for that compatible string. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
DSI1 on BCM2711 doesn't require the DMA workaround that is used on BCM2835/6/7, therefore it needs a new compatible string. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
DSI0 was partially supported, but didn't register with the main driver, and the code was inconsistent as to whether it checked port == 0 or port == 1. Add compatible string and other support to make it consistent. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
Breaks out common register set and adds the different registers for 1280x720 (cropped) and 640x480 (skipped) modes Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
MichaIng authored
CONFIG_WIREGUARD=m implies CONFIG_ARM_CRYPTO=y, hence the latter is removed. Signed-off-by: MichaIng <micha@dietpi.com>
-
Phil Elwell authored
CONFIG_BRIDGE_NETFILTER=m used to be the default when CONFIG_NETFILTER was enabled, but that was removed in 5.9. The way that defconfigs work caused this wanted setting to be lost in rpi-5.9.y and rpi-5.10.y - restore it now. See: https://github.com/Hexxeh/rpi-firmware/issues/248 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
The CAN_ISOTP setting was in the wrong position, and it's better for bisecting and reverting if this doesn't get rolled into the next config-changing commit. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Marc Kleine-Budde authored
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
-
Dave Stevenson authored
Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
In switching to the hardware I2C controller there is an issue where we seem to not get back the correct state from the Pi touchscreen. Insert a delay before polling to avoid this condition. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
We now have the hardware I2C controller pinmuxed to the drive the display I2C, but this controller does not support clock stretching. The Atmel micro-controller in the panel requires clock stretching to allow it to prepare any data to be read. Split the rpi_touchscreen_i2c_read into two independent transactions with a delay between them for the Atmel to prepare the data. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
This touchscreen controller is used by the 7" DSI panel, and this overlay configures it for when it is NOT being polled by the firmware. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
Not all systems have the interrupt line wired up, so switch to polling the touchscreen off a timer if no interrupt line is configured. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dom Cobley authored
Using a hdmi analyser the bytes in packet ram registers beyond the length were visible in the infoframes and it flagged the checksum as invalid. Zeroing unused words of packet RAM avoids this Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Phil Elwell authored
[1] replaced a single reset function with a pointer to one of two implementations, but also removed the call asserting the reset at the start of brcm_pcie_setup. Doing so breaks Raspberry Pis with VL805 XHCI controllers lacking dedicated SPI EEPROMs, which have been used for USB booting but then need to be reset so that the kernel can reconfigure them. The lack of a reset causes the firmware's loading of the EEPROM image to RAM to fail, breaking USB for the kernel. See: https://www.raspberrypi.org/forums/viewtopic.php?p=1758157#p1758157 Fixes: 04356ac3 ("PCI: brcmstb: Add bcm7278 PERST# support") [1] 04356ac3 ("PCI: brcmstb: Add bcm7278 PERST# support") Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Dom Cobley authored
Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
menschel authored
* Add mcp251xfd driver module to the RPi kernel builds. * Add isotp can protocol module to the RPi kernel builds. Signed-off-by: Patrick Menschel <menschel.p@posteo.de>
-