From: Mark Rutland <mark.rutland@arm.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Sebastian Frias <sf84@laposte.net>,
devicetree <devicetree@vger.kernel.org>,
Mason <slash.tmp@free.fr>, LKML <linux-kernel@vger.kernel.org>,
Timur Tabi <timur@tabi.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: ARM, SoC: About the use DT-defined properties by 3rd-party drivers
Date: Mon, 12 Sep 2016 18:06:05 +0100 [thread overview]
Message-ID: <20160912170604.GG14165@leverpostej> (raw)
In-Reply-To: <CANCZdfqZEMRaFqgph6kZPdyxBcURBiEV0XoH0vPG28Hhm5+77A@mail.gmail.com>
Hi,
On Mon, Sep 12, 2016 at 10:45:37AM -0600, 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 guess you don't actually have those written down, but on the
off-chance, would you be able to share any major pain points?
We do try (admittedly far from perfectly) to avoid implementation
details in bindings, but driver mdoel details are fairly difficult to
pin down either way. It would be nice to be more aware.
Thanks,
Mark.
next prev parent reply other threads:[~2016-09-12 17:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 14:29 ARM,SoC: About the use DT-defined properties by 3rd-party drivers Sebastian Frias
2016-08-28 20:36 ` ARM, SoC: " Timur Tabi
2016-09-12 12:29 ` ARM,SoC: " Sebastian Frias
[not found] ` <57D69FB1.2020801-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-12 12:38 ` Mark Rutland
2016-09-12 13:15 ` Sebastian Frias
2016-09-12 13:23 ` Timur Tabi
2016-09-12 14:01 ` ARM, SoC: " Mark Rutland
2016-09-12 14:26 ` Warner Losh
2016-09-12 16:29 ` Sebastian Frias
2016-09-12 16:45 ` Warner Losh
2016-09-12 16:49 ` Timur Tabi
2016-09-12 17:07 ` Mark Rutland
2016-09-12 17:06 ` Mark Rutland [this message]
2016-09-12 16:07 ` Sebastian Frias
[not found] ` <57D6D2A9.3010006-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-12 16:21 ` Timur Tabi
2016-09-12 16:26 ` Sebastian Frias
2016-09-12 16:56 ` Mark Rutland
2016-09-13 10:04 ` Sebastian Frias
[not found] ` <57D7CF17.2050905-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-13 11:37 ` Timur Tabi
[not found] ` <57D7E4EC.6050509-N01EOCouUvQ@public.gmane.org>
2016-09-13 13:23 ` Mark Rutland
2016-09-13 13:12 ` Mark Rutland
2016-09-13 14:22 ` Sebastian Frias
[not found] ` <57D80B91.4020306-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-13 14:51 ` Mark Rutland
2016-09-14 8:32 ` Sebastian Frias
2016-09-13 14:55 ` Sebastian Frias
[not found] ` <57D8137F.8040508-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2016-09-13 15:47 ` Mark Rutland
2016-09-14 8:24 ` Sebastian Frias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160912170604.GG14165@leverpostej \
--to=mark.rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=imp@bsdimp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
--cc=timur@tabi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).