> > > > I'm in favor of dropping the old binding from the schema. New DTs > > should clearly use the new binding and old DTs shouldn't change > > anymore, so validation is less useful there. > > I wonder if it makes sense to have a more standardized hantro schema > for all the users instead of one dedicated to each platform using a > hantro driver. The unified schema could have all the various > compatible flags so the driver still knows which features are > enabled/disabled and it's very clear who all the users are for it. I > would think it could cover both the encoder and decoder variants as > well. We do something similar for 8250 serial ports. > > If so, can someone from the media group suggest the best one to > follow? Ezequiel suggested I look at the sama5d4-vdec to help reduce > some clutter in the driver. If that binding is good enough, should I > just add the compatible flags to that and potentially rename it. > A unified schema might sound elegant and compelling, but I suspect it can bite us down the road, due to differences in the platform integration. Seems we are all on-board going forward with a patch similar to this one, but also dropping the deprecated binding from the schema (while of course still supporting old DTBs on new kernels). Rob's suggestion about having a warning in the platform if the binding has not been updated, sounds like very useful too. Keep in mind v5.16-rc5 is near, which means we still have a few weeks to discuss this patch, until the next linux-media merge season. Thanks, Ezequiel
