On Sat, Aug 26, 2023 at 02:36:29PM +0530, Sughosh Ganu wrote:
Add a function which is registered to spy for a EVT_FT_FIXUP event, and removes the non upstreamed nodes and properties from the devicetree before it gets passed to the OS.
This allows removing entire nodes, or specific properties under nodes from the devicetree. The required nodes and properties can be registered for removal through the DT_NON_COMPLIANT_PURGE and DT_NON_COMPLIANT_PURGE_LIST macros.
Signed-off-by: Sughosh Ganu sughosh.ganu@linaro.org
So, the conceptual problem here is that while we do need to have a way to purge nodes and properties that have been rejected by upstream, we also need to ensure an upstream attempt was made. To that end, how I envision things is: - When we build the docs, something under doc/develop/ has a page / section for each binding we're purging, which links to and summarizes why it's not appropriate for upstream. - It's non-default to purge said nodes. - We at least make checkpatch / et al complain about new purges being added, and CI failing on the number of purges increasing without also increasing the number of allowed purges.