- Jun 18, 2020
-
-
Phil Elwell authored
The CMA handling change broke the audio parameter - the fragment numbering has changed - so fix it. See: https://github.com/raspberrypi/linux/issues/2489 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
The arm bcm2711_defconfig and the arm64 bcmrpi3_defconfig have been missing their NF_TABLES settings. Restore them. See: https://github.com/raspberrypi/linux/issues/3615 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Dave Stevenson authored
V4L2 wishes to have the codec header bytes in the same buffer as the first encoded frame, so it does become 1-in 1-out for encoding. The firmware now has an option to do this, so enable it. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
The firmware by default is quite happy to fragment encoded frames as the original MMAL and IL APIs support this. V4L2 doesn't, so we need to enable the firmware option to avoid this. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
V4L2 wishes to have the codec header bytes in the same buffer as the first encoded frame, so it does become 1-in 1-out for encoding. The firmware now has an option to do this, so enable it. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
Adds in a couple of new MMAL parameter defines. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
Adding the Broadcast RGB range selection broke the VIC field of the AVI infoframes on HDMI, zeroing them for all modes on an HDMI monitor. Correct this so that it is only zeroed if the range is contrary to the standard range of the mode. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Phil Elwell authored
The SC16IS7XX hardware flow control is mishandled by the driver in a number of ways: 1. The set_baud method accidentally clears it when setting EFR bit. 2. Even though hardware flow control is enabled, it isn't indicated back to the serial framework. 3. Applying the flow control clears the EFR bit. 4. The CTS support is not indicated in the return from sc16is7xx_get_mctrl. Address all of those issues using a mixture of patches found on the linked pages. See: https://github.com/raspberrypi/linux/issues/2542 See: https://www.spinics.net/lists/linux-serial/msg21794.html Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Dave Stevenson authored
From when bringing up the driver, there was a check in the isr to ignore interrupts (claiming them handled) should the driver not be streaming. The VPU now will not register a camera driver if it finds a CSI2 node enabled in device tree, therefore this flawed check is redundant. https://github.com/raspberrypi/linux/issues/3602 Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Phil Elwell authored
Switch to the upstream cpufreq driver on non-BCM2835 Pis. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Dave Stevenson authored
The CMA dma-heap allocator can be used in place of vcsm-cma doing the allocation side, thereby simplifying that driver. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Naushir Patuck authored
This commit enables the imx477 sensor driver in the following defconfigs: bcm2709_defconfig bcm2711_defconfig bcmrpi_defconfig bcmrpi3_defconfig Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Naushir Patuck authored
Use V4L2_CID_EXPOSURE_AUTO_PRIORITY to control if the driver should automatically adjust the sensor frame length based on exposure time, allowing variable frame rates and longer exposures. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Naushir Patuck authored
Adds a driver for the 12MPix Sony IMX477 CSI2 sensor. Whilst the sensor supports 2 or 4 CSI2 data lanes, this driver currently only supports 2 lanes. The following Bayer modes are currently available: 4056x3040 12-bit @ 10fps 2028x1520 12-bit (binned) @ 40fps 2028x1050 12-bit (cropped/binned) @ 50fps 1012x760 10-bit (scaled) @ 120 fps Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Naushir Patuck authored
Add an overlay for the Sony IMX477 CMOS sensor device. Also update overlay README and Makefile. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Naushir Patuck authored
Add YAML device tree binding for IMX477 CMOS image sensor. Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
-
Phil Elwell authored
Add the command line options required to enable audio over discrete ALSA devices. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
Apart from some special cases, device objects are only created for nodes if they are children of a bus or the root node. "fixed-clock" is one of the exceptions that will be instantiated wherever it is found, but only during kernel initialisation - ruling out loading the overlay at runtime. Move most of the affected clocks to be children of the root, only leaving those in overlays that could be multiply instantiated, to avoid a potential name clash. See: https://github.com/raspberrypi/linux/issues/3602 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
The tc358743 overlay was written using a workaround to a problem with fragments that target other fragments, but this had the unfortunate side-effect of preventing the overlay from being applied at runtime (the kernel doesn't allow nodes to be overwritten by an overlay, only properties). The current firmware and dtoverlay/dtparam utilities include support for these "intra-overlay" fragments, so remove the workaround and do it properly. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Dom Cobley authored
Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Dom Cobley authored
Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Dom Cobley authored
2711 uses a fixed 27MHz input, earlier models use the HSM clock Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Dom Cobley authored
Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Dom Cobley authored
Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Dom Cobley authored
Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Dom Cobley authored
Fix an incorrect register address, add a missing one and reorder into address order Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Dom Cobley authored
Signed-off-by: Dom Cobley <popcornmix@gmail.com>
-
Phil Elwell authored
The other sc16is75x overlays have an xtal parameter to allow a different crystal frequency to be specified, but sc16is752-spi1 doesn't. Fix this omission. See: https://www.raspberrypi.org/forums/viewtopic.php?f=107&t=273234 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
If the firmware hasn't detected a display, the driver would assume one display was available, but because it had failed to retrieve the display size it would try to allocate a zero-sized buffer. Avoid the allocation failure by bailing out early if no display is found. See: https://github.com/raspberrypi/linux/issues/3598 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Jacko Dirks authored
Signed-off-by: Jacko Dirks <jdirks.linuxdev@gmail.com>
-
Jacko Dirks authored
Signed-off-by: Jacko Dirks <jdirks.linuxdev@gmail.com>
-
Phil Elwell authored
The firmware and runtime overlay support has recently been updated to correctly process fragments that target other fragments within the overlay. Make use of that ability and avoid the use of the awkward target-path = "<alias>/..." workaround and for better readability. Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
popcornmix authored
This is stored in a 6-bit register field which causes a WARN Signed-off-by: popcornmix <popcornmix@gmail.com>
-
Phil Elwell authored
The 32- and 64-bit bcm2711 defconfigs are missing support for the official Raspberry Pi touchscreen. Restore the missing config settings. See: https://github.com/Hexxeh/rpi-firmware/issues/223 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
The arm64 bcm2711_defconfig was inexplicably missing three PPS config options. Add them, along with another missing option from bcmrpi3_defconfig. See: https://github.com/raspberrypi/linux/issues/3593 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Phil Elwell authored
The i2c-gpio driver expects to use a GPIO in open-drain mode. Failure to configure it in that way causes alarming warnings in the kernel log. The BCM283x and BCM2711 GPIO blocks don't support open-drain mode, but i2c-gpio works anyway. Silence the warning by declaring that open-drain mode has been enabled by other means. See: https://github.com/raspberrypi/firmware/issues/1381 Signed-off-by: Phil Elwell <phil@raspberrypi.com>
-
Dave Stevenson authored
The array of potential formats and their configuration should be const. Rework all accesses so that this is possible. The list of supported formats was taking a copy of entries from this table. This is unnecessary, therefore allocate an array of pointers instead of an array of entries. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-
Dave Stevenson authored
With the codec code from which this was derived, the driver had to get the supported formats for both input and output ports. This had been copied across, however here we have independent nodes for each port, but the code had been left in to do the same thing twice. Remove the duplicate. Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
-