From: Maxime Ripard <maxime.ripard@bootlin.com>
To: "André Przywara" <andre.przywara@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <rob.herring@linaro.org>,
devicetree <devicetree@vger.kernel.org>,
Chen-Yu Tsai <wens@csie.org>, Icenowy Zheng <icenowy@aosc.xyz>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Corentin Labbe <clabbe@baylibre.com>
Subject: Re: [PATCH] arm64: dts: allwinner: a64: Re-add "syscon" compatible
Date: Thu, 4 Oct 2018 17:02:37 +0200 [thread overview]
Message-ID: <20181004150237.hsvytl6iycow5xyo@flea> (raw)
In-Reply-To: <22014c5e-fee0-d4c6-bc6c-cd30c8545292@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1502 bytes --]
On Mon, Oct 01, 2018 at 01:55:19AM +0100, André Przywara wrote:
> >> So I am sorry if those things frustrate you (which I can understand
> >> very well), but I believe fixing the DT in a proper way is
> >> much more user friendly in the long term (actually this issue was
> >> brought forward by a user[1]).
> >
> > Given the current state of the industry, I don't really see how the DT
> > can allow you to do what you are trying to achieve.
>
> I am not sure I do understand what you mean with "industry"? If you are
> thinking about the SoC vendor or board vendors to push this endeavor and
> create stable bindings and DTs from the beginning: I see that this won't
> work with the prevalent attitude across many vendors today.
This is what I meant.
> But in our case we (as the community) drive the DTs and the bindings
> anyway, and we decided to mostly ignore Allwinner's DT effort - for good
> reasons. So we can - given consensus on the goals and approach - make
> this possible and don't need to rely on any company or "industry".
Actually, I think this is part of the reason. We like our DT bindings
so much that we are ready to spend monthes debating on it, while with
ACPI (or the DT from the older days, from what I understood) you're
stuck with whatever comes with the board. Whether one likes it or not
doesn't matter. And then you can use whatever kernel with it.
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-10-04 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 15:28 [PATCH] arm64: dts: allwinner: a64: Re-add "syscon" compatible Andre Przywara
2018-09-21 9:47 ` Chen-Yu Tsai
2018-09-21 14:35 ` Andre Przywara
2018-09-21 14:57 ` Chen-Yu Tsai
2018-10-01 0:52 ` André Przywara
2018-09-21 15:16 ` Maxime Ripard
2018-09-24 10:22 ` Andre Przywara
2018-09-26 9:52 ` Maxime Ripard
2018-10-01 0:55 ` André Przywara
2018-10-04 15:02 ` Maxime Ripard [this message]
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=20181004150237.hsvytl6iycow5xyo@flea \
--to=maxime.ripard@bootlin.com \
--cc=andre.przywara@arm.com \
--cc=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@linaro.org \
--cc=wens@csie.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).