Linux Kernel https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.4.94 2014-07-04T17:05:05Z 2014-07-04T17:05:05Z Russell King rmk+kernel@arm.linux.org.uk 2014-07-04T12:23:46Z urn:sha1:b509cc802239a8b5ba7d1d2cc5adfb9d984b7ed8 Sachin Kamat reports that "component: add support for component match array" broke Exynos DRM due to a NULL pointer deref. Fix this. Reported-by: Sachin Kamat <sachin.kamat@samsung.com> Tested-by: Sachin Kamat <sachin.kamat@samsung.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 2014-07-03T10:32:43Z Russell King rmk+kernel@arm.linux.org.uk 2014-04-19T10:18:01Z urn:sha1:6955b58254c2bcee8a7b55ce06468a645dc98ec5 Add support for generating a set of component matches at master probe time, and submitting them to the component layer. This allows the component layer to perform the matches internally without needing to call into the master driver, and allows for further restructuring of the component helper. Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 2014-07-03T10:32:40Z Russell King rmk+kernel@arm.linux.org.uk 2014-04-18T19:16:22Z urn:sha1:fcbcebce7159c928692dc6a5e88869f6e44438b9 Permit masters to call component_master_add_child() and match the same child multiple times. This may happen if there's multiple connections to a single component device from other devices. In such scenarios, we should not return a failure, but instead ignore the attempt. Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 2014-07-03T10:32:37Z Russell King rmk+kernel@arm.linux.org.uk 2014-04-23T09:52:17Z urn:sha1:c334940ea26cb58f5514dcbb225a3f397b2684ad In try_to_bring_up_master(), we tear down the master's component list for each error case, except for devres group failure. Fix this oversight by making the code less prone to such mistakes. Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 2014-02-08T00:45:14Z Russell King rmk+kernel@arm.linux.org.uk 2014-02-07T20:09:27Z urn:sha1:9e1ccb4a7700fcb3ddfe2767e0bbb6131f8ab54e We weren't handling the devres issues for the master device failing a bind, or being unbound properly. Add a devres group to contain these, and release the resources at the appropriate points. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2014-01-11T00:27:36Z Russell King rmk+kernel@arm.linux.org.uk 2014-01-10T23:23:37Z urn:sha1:2a41e6070dd7ef539d0f3b1652b4839d04378e11 Subsystems such as ALSA, DRM and others require a single card-level device structure to represent a subsystem. However, firmware tends to describe the individual devices and the connections between them. Therefore, we need a way to gather up the individual component devices together, and indicate when we have all the component devices. We do this in DT by providing a "superdevice" node which specifies the components, eg: imx-drm { compatible = "fsl,drm"; crtcs = <&ipu1>; connectors = <&hdmi>; }; The superdevice is declared into the component support, along with the subcomponents. The superdevice receives callbacks to locate the subcomponents, and identify when all components are present. At this point, we bind the superdevice, which causes the appropriate subsystem to be initialised in the conventional way. When any of the components or superdevice are removed from the system, we unbind the superdevice, thereby taking the subsystem down. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>