On Wednesday 04 September 2013 11:29:00, Stephen Warren wrote: > On 09/02/2013 03:38 AM, Lars Poeschel wrote: > > Am Freitag, 30. August 2013, 13:53:45 schrieb Stephen Warren: > ... > > >> Yet the current patch only addresses a limited set of cases, since it > >> doesn't hook the APIs but rather parses the DT. It doesn't cover the > >> non-DT case. It should if the feature is useful. > > > > As pointed out before, only DT has this problem, that, > > That's completely false. Both DT and non-DT can represent the exact same > HW, and use the exact same drivers. It's equally possible to write a bug > in a board file or a DT file (i.e. a typo or incorrect reading of the > schematic) that causes the wrong GPIO or IRQ ID to be used, and hence > for there to be conflicts. Any solution to this issue needs to address > both cases. This is again not the point. This is not what this patch is trying to solve. The patch is trying to solve problem A. But you are talking about problem B. Sure I can write a bug in board files and I can write a bug in DT files. The patch is not trying to prevent that. This is a completly different thing. -- 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
