On Wed, Aug 01, 2018 at 06:08:07PM +0300, Dmitry Osipenko wrote: > From time to time new bugs are popping up, causing some host1x client to > fail its initialization. Currently a single clients initialization failure > causes whole host1x device registration to fail, as a result a single DRM > sub-device initialization failure makes whole DRM initialization to fail. > Let's ignore clients initialization failure, as a result display panel > lights up even if some DRM clients (say GR2D or VIC) fail to initialize. > > Signed-off-by: Dmitry Osipenko <digetx@xxxxxxxxx> > --- > drivers/gpu/host1x/bus.c | 18 +++++++----------- > 1 file changed, 7 insertions(+), 11 deletions(-) This is actually done on purpose. I can't think of a case where we would actively like to keep a half-broken DRM device operational. The errors that you're talking about should only happen during development, and the device not showing up is a pretty good indicator that something is wrong as opposed to everything booting normally and then getting some cryptic error at runtime because one of the clients didn't initialize. From my perspective, all clients should always be operational in whatever baseline version you use. If it isn't that's a bug that should be fixed. Ideally those bugs should get fixed before making it into a baseline version (mainline, linux-next, ...), so that this never impacts even developers, unless they break it themselves, in which case refusing to register the DRM device is a pretty good incentive to fix it. Thierry
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
