From mboxrd@z Thu Jan 1 00:00:00 1970 From: swarren@wwwdotorg.org (Stephen Warren) Date: Fri, 25 Oct 2013 15:44:09 +0100 Subject: [RFC PATCH dtc] C-based DT schema checker integrated into dtc In-Reply-To: <20131024234340.ADF70C403B6@trevor.secretlab.ca> References: <1382651488-9696-1-git-send-email-swarren@wwwdotorg.org> <20131024234340.ADF70C403B6@trevor.secretlab.ca> Message-ID: <526A83B9.30800@wwwdotorg.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 10/25/2013 12:43 AM, Grant Likely wrote: > On Thu, 24 Oct 2013 22:51:28 +0100, Stephen Warren wrote: >> From: Stephen Warren >> >> This is a very quick proof-of-concept re: how a DT schema checker might >> look if written in C, and integrated into dtc. > > Thanks for looking at this. > > Very interesting. Certainly an expedient way to start checking schemas, > and for certain bindings it may be the best approach. The downside is it > forces a recompilation of DTC to bring in new bindings and it isn't a > great meduim for mixing schema with documentation in the bindings. This approach would certainly require recompiling something. I threw the code into dtc simply because it was the easiest container for the demonstration. It could be a separate DT validation utility if we wanted, although we'd need to split the DT parser from dtc into a library to avoid code duplication. The resultant utility could be part of the repo containing the DTs, so it didn't end up as a separate package to manage. I think the additional documentation could be added as comments in the validation functions, just like IIRC it was to be represented as comments even in the .dts-based schema proposals.