- Jun 26, 2019
-
-
Mariusz Bialonczyk authored
commit aacd152e upstream. This commit is fixing a smatch warning: drivers/w1/slaves/w1_ds2413.c:61 state_read() warn: impossible condition '(*buf == 255) => ((-128)-127 == 255)' by creating additional u8 variable for the bus reading and comparision Reported-by:
kbuild test robot <lkp@intel.com> Reported-by:
Dan Carpenter <dan.carpenter@oracle.com> Cc: Dan Carpenter <dan.carpenter@oracle.com> Fixes: 3856032a ("w1: ds2413: when the slave is not responding during read, select it again") Signed-off-by:
Mariusz Bialonczyk <manio@skyboo.net> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Mariusz Bialonczyk authored
commit 3856032a upstream. The protocol is not allowing to obtain a byte of 0xff for PIO_ACCESS_READ call. It is very likely that the slave was not addressed properly and it is just not respoding (leaving the bus in logic high state) during the read of sampled PIO value. We cannot just call w1_reset_resume_command() because the problem will persist, instead try selecting (addressing) the slave again. Signed-off-by:
Mariusz Bialonczyk <manio@skyboo.net> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Mariusz Bialonczyk authored
commit c50d09a8 upstream. The state_read() was calling PIO_ACCESS_READ once and bail out if it failed for this first time. This commit is improving this to trying more times before it give up, similarly as the write call is currently doing. Signed-off-by:
Mariusz Bialonczyk <manio@skyboo.net> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Mariusz Bialonczyk authored
commit ae2ee27a upstream. Make the output_write simpler. Based on Jean-Francois Dagenais code from: 49695ac4 ("w1: ds2408: reset on output_write retry with readback") Signed-off-by:
Mariusz Bialonczyk <manio@skyboo.net> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Mariusz Bialonczyk authored
commit 0e3743d8 upstream. The ds2805 has a structure named: w1_family_2d, which surely comes from a w1_ds2431 module. This commit fixes this name to prevent confusion and mark a correct family name. Signed-off-by:
Mariusz Bialonczyk <manio@skyboo.net> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Phil Elwell authored
The dwc2 overlay no longer uses the dwc2_usb label, and the latest ovmerge (which generates the upstream overlay) removes unused labels. Update the checked-in version to match. Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
See: https://github.com/raspberrypi/linux/issues/3013 Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
Kernels since 4.19 have required the correct manufacture name in the compatible string for I2C devices, and unfortunately the one for the Dallas/Maxim DS1307 should have been "dallas,ds1307" and not "maxim,ds1307". See: https://github.com/raspberrypi/linux/issues/3013 Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
I've attempted to follow the upstream conventions in the DT commits, but this is just presented here initially as a talking point. Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
1) The top-level .dts files now include parallel chains of bcm27xx.dtsi and bcm27xx-rpi.dtsi files, with no cross-inclusion between the two chains. 2) Move definitions and deletions to the point of maximum commonality to reduce redundancy. Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Dave Stevenson authored
Selecting 1080p100 and 120 has very limited gain, but don't want to block VGA85 and similar. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
dp111 authored
It appears to me the addresses for the gic400 are slightly wrong . See section 3.2 https://static.docs.arm.com/ddi0471/a/DDI0471A_gic400_r0p0_trm.pdf
-
Phil Elwell authored
Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Dave Stevenson authored
Incorrect masking was used in the switch for the modifier, therefore for SAND (which puts the column pitch in the modifier) it didn't match. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
Dave Stevenson authored
Previously multiple displays were slaved off the same SMI interrupt, triggered by HVS channel 1 (HDMI0). This doesn't work if you only have a DPI or DSI screen (HVS channel 0), and gives slightly erroneous results with dual HDMI as the events for HDMI1 are incorrect. Use SMIDSW0 and SMIDSW1 registers to denote which display has triggered the vblank. Handling should be backwards compatible with older firmware. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
Jonathan Bell authored
Lets the mousepoll override mechanism work with xhci. Signed-off-by:
Jonathan Bell <jonathan@raspberrypi.org>
-
Jonathan Bell authored
Must be called in a non-atomic context, after the endpoint has been registered with the hardware via xhci_add_endpoint and before the first URB is submitted for the endpoint. Signed-off-by:
Jonathan Bell <jonathan@raspberrypi.org>
-
Jonathan Bell authored
xHCI caches device and endpoint data after the interface is configured, so an explicit command needs to be issued for any device driver wanting to alter the polling interval of an endpoint. Add usb_fixup_endpoint() to allow drivers to do this. The fixup must be called after calculating endpoint bandwidth requirements but before any URBs are submitted. If polling intervals are shortened, any bandwidth reservations are no longer valid but in practice polling intervals are only ever relaxed. Limit the scope to interrupt transfers for now. Signed-off-by:
Jonathan Bell <jonathan@raspberrypi.org>
-
Dave Stevenson authored
Firmware TMDS scrambling is now being correctly configured, so we can use it. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
Phil Elwell authored
Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Dave Stevenson authored
The firmware sets up simple fb should one of the KMS drivers be enabled, but the driver isn't being built. Add it to the build. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
Dave Stevenson authored
The wrong vc_image formats were being checked for in the switch statement. Correct these. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
Dave Stevenson authored
Without the include the peripheral is configured to have 0 data lanes, which doesn't allow much data to be passed. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
Dave Stevenson authored
Lots of things like USB DVB tuners were missing from the defconfig. Resync it with bcm2709_defconfig Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
Phil Elwell authored
Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
The updated bcm2835-dma driver does not require the BULK channel to be removed from the set of available channels, as provided by dma-channel-mask. Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
The 40-bit additions are not fully tested, but it should be capable of supporting both 40-bit memcpy on BCM2711 and regular Lite channels on BCM2835. Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Jonathan Bell authored
Signed-off-by:
Jonathan Bell <jonathan@raspberrypi.org>
-
Phil Elwell authored
This commit adds initial support for 64-bit 2711 builds. However, it will only work as much as it does if the Pi4 RAM is limited to 1GB - more than that and several things break (SD card, coherent allocations, etc.) Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
-
Phil Elwell authored
-
Tim Gover authored
The 2711 B0 boot EEPROM is programmed via SPI0 on GPIO pins 40-43 CS0. Add a device tree overlay to optionally change the SPI0 pinmux from the external GPIO pins to the boot EEPROM pins.
-
Martin Sperl authored
Signed-off-by:
Martin Sperl <kernel@martin.sperl.org>
-
Phil Elwell authored
Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Phil Elwell authored
Signed-off-by:
Phil Elwell <phil@raspberrypi.org>
-
Stefan Wahren authored
We want all common BCM2835/6/7/8 functions in bcm283x.dtsi and all BCM2835/6/7 specific in the new bcm2835-common.dtsi. Signed-off-by:
Stefan Wahren <wahrenst@gmx.net>
-
James Hughes authored
-
Dave Stevenson authored
The allocation code had been copied in from an old branch prior to having added the IDR for 64bit support. It was therefore pushing a pointer into the kernel_id field instead of an IDR handle, the lookup therefore failed, and we never released the buffer. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-
Dave Stevenson authored
They weren't errors but were logged as such. Signed-off-by:
Dave Stevenson <dave.stevenson@raspberrypi.org>
-