On Wed, Sep 21, 2016 at 06:54:59AM +0000, Po Liu wrote: > > > > Will the new kernel work with existing/old DTB? I'm trying to > > > > understand the dependency between driver and DTS changes. > > > > > > Yes, We've never use name 'intr' before. So we remove it is ok. > > > 'aer' is a dts name for researching it's true interrupt number by > > kernel. This patch is first time to use name 'aer'. So it must be > > compatible with existing/old DTB. > > > > Does that mean driver and DTS changes can go through separate trees, i.e. > > PCI and arm-soc, without introducing regressions on either tree? > > Or does the patch series needs to go in as a whole? > > Should be as a whole. The driver base on the dts. Or else, the driver would not found the 'aer' point. Let me try to understand this one more time. So if the new kernel boots with an existing DTB, the driver will fail to find 'aer' interrupt, right? My question is that in this case, the driver will just stop working or keep working in the same way as old kernel. The former case is a regression which breaks old DTB support, and the latter is pretty much like that we are adding a new support, and the DTS change can go independently with driver part through different subsystem tree. Hope I make my question clear this time. Shawn -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
