linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rodrigo Exterckötter Tjäder" <rodrigo@tjader.xyz>
To: maxime.ripard@bootlin.com
Cc: wens@csie.org, robh+dt@kernel.org, mark.rutland@arm.com,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: allwinner: Olimex A64-OLinuXino: enable eMMC.
Date: Thu, 15 Nov 2018 12:46:06 -0200	[thread overview]
Message-ID: <CAG7TQgGO-CjPE6SAUa53GYhMr5-yVe0YaAL3UV15E+f9kKZVwA@mail.gmail.com> (raw)
In-Reply-To: <20181005154844.234g5k3fw5txqxsl@flea>

On Fri, Oct 5, 2018 at 12:48 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> > What about the idea of keeping the current dt for the most featureful
> > variant and creating new dts for the other two?
> >
> > That would make it so that no one's device stops working and would
> > have mailine support for all three devices.
>
> IIRC that has been the first introduced version, so that would make
> sense. Chen-Yu, any opinion?
>
> > Also, the current device tree doesn't represent any existing device:
> > it has wifi on but no emmc. That variation does not exist.
>
> Most of our device tree are far from complete, so you shouldn't treat
> them as such.

So, any agreement on what is to be done about the devices tree for the
A64-OLinuXino devices?

In my opinion the best path would be keeping the current dt for the
most featureful variant and creating new dts for the other two.

      reply	other threads:[~2018-11-15 14:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 14:18 [PATCH 1/2] arm64: dts: allwinner: Olimex A64-OLinuXino: enable eMMC Rodrigo Exterckötter Tjäder
2018-09-21 14:28 ` Maxime Ripard
2018-09-21 14:54   ` Rodrigo Exterckötter Tjäder
2018-09-25  9:01     ` Maxime Ripard
2018-09-25 17:47       ` Rodrigo Exterckötter Tjäder
2018-09-27  8:17         ` Maxime Ripard
2018-09-27 14:49           ` Rodrigo Exterckötter Tjäder
2018-09-29 15:47             ` Maxime Ripard
2018-09-29 16:51               ` Rodrigo Exterckötter Tjäder
2018-10-02 13:13                 ` Maxime Ripard
2018-10-02 16:47                   ` Rodrigo Exterckötter Tjäder
2018-10-05 15:48                     ` Maxime Ripard
2018-11-15 14:46                       ` Rodrigo Exterckötter Tjäder [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=CAG7TQgGO-CjPE6SAUa53GYhMr5-yVe0YaAL3UV15E+f9kKZVwA@mail.gmail.com \
    --to=rodrigo@tjader.xyz \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=robh+dt@kernel.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).