From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers Date: Mon, 12 Sep 2016 11:49:07 -0500 Message-ID: <57D6DC83.8020000@tabi.org> References: <57BDAF2E.10502@laposte.net> <57D69FB1.2020801@laposte.net> <20160912123809.GB13741@leverpostej> <57D6AA54.6000208@laposte.net> <20160912135549.GA14165@leverpostej> <57D6D7D2.7030507@laposte.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Warner Losh , Sebastian Frias Cc: Mark Rutland , devicetree , Mason , Linux ARM , LKML List-Id: devicetree@vger.kernel.org Warner Losh wrote: > Do I have more examples > where FreeBSD has to deviate because the DT is actually Linux > specific and does a poor job of modeling the hardware and instead > reflects the Linux driver model? I have plenty of those... I think it would be a great idea if the FreeBSD and Linux DT maintainers collaborated on cleaning up the DT bindings so that this problem no longer occurs (or at least, not normally). I would love to see some of those examples.