public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Andre 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: Wed, 26 Sep 2018 11:52:02 +0200	[thread overview]
Message-ID: <20180926095202.tdibor3x7fsn6afz@flea> (raw)
In-Reply-To: <20180924112230.73e3009b@donnerap.Emea.Arm.com>

On Mon, Sep 24, 2018 at 11:22:30AM +0100, Andre Przywara wrote:
> > The fundamental difference is that we're mostly just a bunch of spare
> > time programmers working on this platform, with a partial
> > documentation for the controllers, at best.
> > 
> > You forced me to ask these developpers to work on their weekends and
> > evenings on some crazy corner cases to maintain the backward
> > compatibility. And honestly, both from a technical and human
> > standpoint, I definitely understand if some of them are just leaving
> > and don't want to work on it anymore. I would probably do the same in
> > their position.
> > 
> > And having to ask that for companies like ARM or SUSE just makes it
> > more frustrating to be honest. So there's simply no way you have
> > forward compatibility while I'm there. Or you manage to convince all
> > the ARM maintainers and enforce that compatibility for all the
> > platforms.
> 
> I understand that from your point of view there is no way of investing
> huge efforts in staying forward compatible, but I am not asking for
> that (and by no way forcing this!). Instead this suggestion is a small
> tweak to achieve this.

We're trying to remain compatible but if there's any technical reason,
then we won't be. I don't want anyone to assume we will, and to rely
on the fact that we are actually guaranteeing this.

> 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.

Maxime

-- 
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-09-26  9:52 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 [this message]
2018-10-01  0:55           ` André Przywara
2018-10-04 15:02             ` Maxime Ripard

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=20180926095202.tdibor3x7fsn6afz@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