From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754530AbcILQtP (ORCPT ); Mon, 12 Sep 2016 12:49:15 -0400 Received: from muin.pair.com ([209.68.1.55]:50081 "EHLO muin.pair.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754366AbcILQtN (ORCPT ); Mon, 12 Sep 2016 12:49:13 -0400 Subject: Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers To: Warner Losh , Sebastian Frias Cc: Mark Rutland , devicetree , Mason , Linux ARM , LKML References: <57BDAF2E.10502@laposte.net> <57D69FB1.2020801@laposte.net> <20160912123809.GB13741@leverpostej> <57D6AA54.6000208@laposte.net> <20160912135549.GA14165@leverpostej> <57D6D7D2.7030507@laposte.net> From: Timur Tabi Message-ID: <57D6DC83.8020000@tabi.org> Date: Mon, 12 Sep 2016 11:49:07 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@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.