On 10/13/2013 11:58 PM, Terje Bergström wrote: > On 12.10.2013 01:43, Stephen Warren wrote: >> On 10/07/2013 02:34 AM, Thierry Reding wrote: >>> The gr2d hardware in Tegra114 is compatible with that of Tegra20 and >>> Tegra30. No functionaly changes are required. >> >> Similarly here, if the HW is 100% backwards-compatible, there's no need >> to add compatible values to the driver. > > We've used this mechanism for attaching a per-hw-version data structure > in match table to accomodate differences in how the hardware is power > gated, reset, booted, some per-soc performance related changes etc. If there are differences in those aspects of the HW, such that a driver written only to the full specification of e.g. Tegra30 would not work on Tegra114, then the HW is not actually compatible, and hence we do need multiple compatible values in DT, and entries in the of_match table. It sounds like the statement in the commit description: >>> The gr2d hardware in Tegra114 is compatible with that of Tegra20 and >>> Tegra30. No functionaly changes are required. Might not be absolutely accurate in terms of HW, but only in terms of the features that the driver uses so far. It'd be good to explicitly qualify this in the commit description. ... > Upstream driver is not yet in a state where that is relevant. The compatible values should be picked based on the full feature-set of the HW, not based on the subset of features supported by a particular driver. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
