payload: {"push_id":3730523733,"size":563,"distinct_size":563,"ref":"refs/heads/master","head":"c0e4c41afeef66d21dc5704f614624cecac806ac","before":"1c6b40509daf5190b1fd2c758649f7df1da4827b","commits":[{"sha":"768f719ab7b045e30055be3b4ceb2fcf9ceb58f2","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: fix crtc interlace\n\nWe support interlace, but this was broken when we could no longer get\na ref on the vblank interrupt.  Arrange to get the ref on the vblank\ninterrupt after we've re-enabled vblank, and put it before we disable\nthe vblank.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/768f719ab7b045e30055be3b4ceb2fcf9ceb58f2"},{"sha":"ad52f53ff4e3167425b4b2195a23b9d2d0d243c6","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: use __drm_atomic_helper_plane_reset in overlay reset\n\nUse the __drm_atomic_helper_plane_reset() helper in the overlay reset\ncode to ensure that generic features are correctly reset in future.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/ad52f53ff4e3167425b4b2195a23b9d2d0d243c6"},{"sha":"9184ae8db3d563438519cab295c2c9698255ca87","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: add plane size/location accessors\n\nAdd accessors for getting the register values for the plane from the\nplane state.  This will allow us to generate the values when validating\nthe plane rather than when programming, which allows us to fix the\ninterlace handling without adding lots of additional handling in the\nupdate functions.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/9184ae8db3d563438519cab295c2c9698255ca87"},{"sha":"1d1547ec12bc7d4d03c21704d4445aff8bcac8c1","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: fix plane location and size for interlace\n\nWhen the CRTC is programmed for interlace, we have to halve the Y\nparameters for the plane.  Rather than doing this in the update\nfunction (which would need the calculation repeated for the old\nstate as well as the new state), arrange to do the calculation in\natomic_check and save it in our private plane state structure.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/1d1547ec12bc7d4d03c21704d4445aff8bcac8c1"},{"sha":"89e0c53ccfbcca4a492d98735d2eda307368f742","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: add missing interlaced support for overlay frame\n\nInterlaced support has been missing from the overlay frame, which is\nsub-optimal.  Add support for this missing feature.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/89e0c53ccfbcca4a492d98735d2eda307368f742"},{"sha":"7d62237da6ec072292c2f738ebffbf10f6a101cf","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: move plane address and pitch calculation to atomic_check\n\nMove the plane address and pitch calculations to atomic_check rather\nthan the update function, so we don't have to probe the interlace\nsetting for the CRTC while updating the plane.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/7d62237da6ec072292c2f738ebffbf10f6a101cf"},{"sha":"d0d765dec6b7e6dc5d6c153784f1a80a1f5bf3c5","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: add support for setting gamma\n\nAdd support for setting gamma through both the legacy interfaces and\nthe atomic interfaces.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/d0d765dec6b7e6dc5d6c153784f1a80a1f5bf3c5"},{"sha":"5d32b660c839706fd9a3d4b0e65cb648bc07032d","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: add comments about HWC32 cursor colour format\n\nAdd some comments about the format of the HWC32 cursor colour format.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/5d32b660c839706fd9a3d4b0e65cb648bc07032d"},{"sha":"f79d7c9543d2318aff29edd1bbcc142301eb75c2","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: add drm_mode_set_crtcinfo() mode fixup\n\nAdd a drm_mode_set_crtcinfo() call in our CRTC's mode_fixup callback\nto ensure that any adjustments to the mode made by connectors etc are\nproperly accounted for by the CRTC.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/f79d7c9543d2318aff29edd1bbcc142301eb75c2"},{"sha":"5a6cbce823bfa13f4ef47049b9ba861e432d5bd2","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: add and use definitions for RDREG4F\n\nAdd and use bit definitions for RDREG4F on Dove Armada 510.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/5a6cbce823bfa13f4ef47049b9ba861e432d5bd2"},{"sha":"0ab17499b18f4b990600be177058957ab1681808","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: add drm_atomic_helper_shutdown() call in tear-down\n\nEnsure that the hardware is disabled prior to tearing down the modeset\nsupport.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/0ab17499b18f4b990600be177058957ab1681808"},{"sha":"7f07ce0f04e25cd41a85ee780dbe85b40c9e3482","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: add CRTC mode validation\n\nAdd CRTC mode validation to reject modes that the CRTC does not support.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/7f07ce0f04e25cd41a85ee780dbe85b40c9e3482"},{"sha":"4ab26d0b244f1109e3a849382c241d8c6da37bbf","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: improve Dove clock selection\n\nImprove the Dove (Armada 510) LCD clock selection and divider\ncalculation, limiting to the valid divisor values, and reporting an\nerror if the clock is not achievable within the bounds of HDMI\nclocking requirements.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/4ab26d0b244f1109e3a849382c241d8c6da37bbf"},{"sha":"b2086ba5c94dfd8330a348872d94023edb96580a","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: use mode_valid to validate the adjusted mode\n\nValidate the adjusted mode in the CRTC mode_fixup() call to ensure that\nany encoder or bridge doesn't supply us with a mode we can't support.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/b2086ba5c94dfd8330a348872d94023edb96580a"},{"sha":"060c754bd29137aac73cff927f213ccdb25c7686","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: redo CRTC debugfs files\n\nMove the CRTC debugfs files into the CRTC specific directory.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/060c754bd29137aac73cff927f213ccdb25c7686"},{"sha":"1e3695dd8e542ab9a2844c76ad1abb1b9b00cb67","author":{"name":"Lubomir Rintel","email":"c9b9bbc6e9b0bc7e9cec5af1551c7b98adb9530c@v3.sk"},"message":"drm/armada: replace the simple-framebuffer\n\nIf there's a simple-framebuffer carried over from boot firmware, it's going\nto stop working once we setup the LCDC for use via DRM. Kick it off from\nthe hardware.\n\nSigned-off-by: Lubomir Rintel <lkundrak@v3.sk>\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/1e3695dd8e542ab9a2844c76ad1abb1b9b00cb67"},{"sha":"38cecb59b6e4ec696fc63a6385f4c2f6937d677b","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: use for_each_endpoint_of_node() to walk crtc endpoints\n\nRather than having a nested set of for_each_child_of_node() walkers,\nuse the graph walker to iterate through the endpoints for CRTCs.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/38cecb59b6e4ec696fc63a6385f4c2f6937d677b"},{"sha":"7add804708b2e09105181d3157ad76a88cc9ffad","author":{"name":"Russell King","email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@armlinux.org.uk"},"message":"drm/armada: no need to check parent of remote\n\nThere's no need to check the parent of the remote device to check\nwhether it is available or not, the remote is the device itself.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/7add804708b2e09105181d3157ad76a88cc9ffad"},{"sha":"f7b0bc5eafa44941ddf92df6f46dd82cbfacec3e","author":{"name":"Nick Crews","email":"48ca69ad9949642e03f749e7c340a20c2a58458c@chromium.org"},"message":"platform/chrome: wilco_ec: Add event handling\n\nThe Wilco Embedded Controller can create custom events that\nare not handled as standard ACPI objects. These events can\ncontain information about changes in EC controlled features,\nsuch as errors and events in the dock or display. For example,\nan event is triggered if the dock is plugged into a display\nincorrectly. These events are needed for telemetry and\ndiagnostics reasons, and for possibly alerting the user.\n\nThese events are triggered by the EC with an ACPI Notify(0x90),\nand then the BIOS reads the event buffer from EC RAM via an\nACPI method. When the OS receives these events via ACPI,\nit passes them along to this driver. The events are put into\na queue which can be read by a userspace daemon via a char device\nthat implements read() and poll(). The event queue acts as a\ncircular buffer of size 64, so if there are no userspace consumers\nthe kernel will not run out of memory. The char device will appear at\n/dev/wilco_event{n}, where n is some small non-negative integer,\nstarting from 0. Standard ACPI events such as the battery getting\nplugged/unplugged can also come through this path, but they are\ndealt with via other paths, and are ignored here.\n\nTo test, you can tail the binary data with\n$ cat /dev/wilco_event0 | hexdump -ve '1/1 \"%x\\n\"'\nand then create an event by plugging/unplugging the battery.\n\nSigned-off-by: Nick Crews <ncrews@chromium.org>\nSigned-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/f7b0bc5eafa44941ddf92df6f46dd82cbfacec3e"},{"sha":"1210d1e6bad1e7ccccb19627b880a50d7c15dd51","author":{"name":"Nick Crews","email":"48ca69ad9949642e03f749e7c340a20c2a58458c@chromium.org"},"message":"platform/chrome: wilco_ec: Add telemetry char device interface\n\nThe Wilco Embedded Controller is able to send telemetry data\nwhich is useful for enterprise applications. A daemon running on\nthe OS sends a command to the EC via a write() to a char device,\nand can read the response with a read(). The write() request is\nverified by the driver to ensure that it is performing only one\nof the whitelisted commands, and that no extraneous data is\nbeing transmitted to the EC. The response is passed directly\nback to the reader with no modification.\n\nThe character device will appear as /dev/wilco_telemN, where N\nis some small non-negative integer, starting with 0. Only one\nprocess may have the file descriptor open at a time. The calling\nuserspace program needs to keep the device file descriptor open\nbetween the calls to write() and read() in order to preserve the\nresponse. Up to 32 bytes will be available for reading.\n\nFor testing purposes, try requesting the EC's firmware build\ndate, by sending the WILCO_EC_TELEM_GET_VERSION command with\nargument index=3. i.e. write [0x38, 0x00, 0x03]\nto the device node. An ASCII string of the build date is\nreturned.\n\nSigned-off-by: Nick Crews <ncrews@chromium.org>\nSigned-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>","distinct":true,"url":"https://api.github.com/repos/ColinIanKing/linux-next-mirror/commits/1210d1e6bad1e7ccccb19627b880a50d7c15dd51"}]}
other: {"actor":{"display_login":"ColinIanKing"}}