On Wed, Apr 17, 2024 at 11:12:09AM +0200, Herman van Hazendonk wrote: > This happens in the MSM DRM driver when it is used > without any subcomponents, which is a special corner > case. > > If the MDP4 is used with nothing but the LVDS display, > we get this problem that no components are found since > the LVDS is part of the MDP4 itself. > > We cannot use a NULL match, so create a dummy match > with no components for this case so the driver will > still probe nicely without adding a secondary > complicated probe() path to the MSM DRM driver. > > Signed-off-by: Linus Walleij <linus.walleij@xxxxxxxxxx> > Signed-off-by: Herman van Hazendonk <github.com@xxxxxxxxxx> > --- > This happens in the MSM DRM driver when it is used > without any subcomponents, which is a special corner > case. > > If the MDP4 is used with nothing but the LVDS display, > we get this problem that no components are found since > the LVDS is part of the MDP4 itself. > > We cannot use a NULL match, so create a dummy match > with no components for this case so the driver will > still probe nicely without adding a secondary > complicated probe() path to the MSM DRM driver. Why is the text duplicated here twice? Also, why are you adding complexity to the core for something that has not been an issue for any other device? Shouldn't the driver need to handle this instead if it wishes to use the component code? Will this change affect any other in-tree user? thanks, greg k-h
