public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 13/20] Revert: arm64: allwinner: a64: pine64: Use dcdc1 regulator for mmc0
Date: Fri, 2 Mar 2018 16:24:22 +0000	[thread overview]
Message-ID: <fe7ffa8a-e8cd-d02c-17f9-28a957b59784@arm.com> (raw)
In-Reply-To: <20180302155850.nhkjhzontzvvlavz@flea.lan>

Hi,

On 02/03/18 15:58, Maxime Ripard wrote:
> On Fri, Mar 02, 2018 at 12:56:52AM +0000, Andre Przywara wrote:
>> Linux kernels before 4.12-rc1 don't know about the AXP803 PMIC, so can't
>> enable the MMC driver with the current DT anymore, because that now
>> depends on this regulator.
> 
> Given that only I2C, USB and MMC were supported at the time, is it
> really worth it? There's a lot of incentive to move to a newer kernel
> given the minimal support it had at the time.

Yeah, this is somewhat true, although serial, USB and MMC are somewhat
enough if one uses a USB Ethernet or WiFi adapter. And the kernel choice
might not always a decision of the user (thinking of distributions here).
But I was actually unsure about this as well, and wanted to hear some
opinions.

One thing that comes to mind is other OSes. Does anyone know how if for
instance FreeBSD supports the AXP and its Linux bindings? The whole goal
of this series is to allow booting OSes with U-Boot's DT copy
($fdtcontroladdr), so if this patch would make their life easier, it
might be worth it.

Regarding the whole forward/backward compatibility:
I clearly see the difficulty in coming up with a "perfect" DT from day
one, especially for badly documented SoCs, where mainlining is driven by
hobbyists. So I was wondering if we introduce a grace period, where we
declare the DT "unstable" or "subject to incompatible changes" for some
releases (not too many). In hindsight we might declare 4.12 the stable
DT base for the A64, for instance.
This would allow us to start upstreaming early, with a small feature set
only (just serial + clocks + pinctrl, as for the H6). Additional
features (PMIC) might then add small incompatibilities (like this one
here), until we are reasonably confident about the DT.
Does that sound useful?

So I am not insisting on this patch, but wanted to point out the
problems that those seemingly innocent DT changes create and would be
happy if we can at least try to avoid them in the future.

Cheers,
Andre.

  reply	other threads:[~2018-03-02 16:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02  0:56 [U-Boot] [PATCH v3 00/20] sunxi: sync H3, H5, A64 DTs from mainline Linux Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 01/20] sunxi: README.sunxi64: Add hint about non-debug of ARM Trusted Firmware Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 02/20] sunxi: gpio: add missing compatible strings Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 03/20] net: sun8i-emac: support new pinctrl DT bindings Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 04/20] net: sun8i-emac: add support for new EMAC DT binding Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 05/20] arm: dts: sunxi: update A64 to new EMAC binding Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 06/20] arm: dts: sunxi: update H3 " Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 07/20] arm: dts: sunxi: update H5 " Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 08/20] net: sun8i-emac: remove support for old binding Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 09/20] sunxi: disable direct MMC environment for 64 bit boards Andre Przywara
2018-03-02 15:56   ` Maxime Ripard
2018-03-02 16:00     ` Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 10/20] sunxi: revert disabling of features Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 11/20] sunxi: DT: A64: update device tree file for Allwinner A64 SoC Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 12/20] sunxi: DT: A64: update board .dts files from Linux Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 13/20] Revert: arm64: allwinner: a64: pine64: Use dcdc1 regulator for mmc0 Andre Przywara
2018-03-02 15:58   ` Maxime Ripard
2018-03-02 16:24     ` Andre Przywara [this message]
2018-03-02 16:32       ` [U-Boot] [linux-sunxi] " Vincent Legoll
2018-03-02 16:42         ` Andre Przywara
2018-03-03 14:59       ` [U-Boot] " Emmanuel Vadot
2018-03-09  9:50       ` Maxime Ripard
2018-03-02  0:56 ` [U-Boot] [PATCH v3 14/20] sunxi: dts: A64 boards: Use fixed " Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 15/20] sunxi: DT: update device tree files for Allwinner H3 and H5 SoCs Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 16/20] sunxi: DT: H5: update board .dts files from Linux Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 17/20] sunxi: DT: H3: " Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 18/20] sunxi: DT: H3: update libre-cc board .dts file Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 19/20] sunxi: DT: H2+: update Opi-zero .dts Andre Przywara
2018-03-02  0:56 ` [U-Boot] [PATCH v3 20/20] sunxi: DT: A64: add proper SoPine baseboard device tree Andre Przywara
2018-03-02 15:59 ` [U-Boot] [PATCH v3 00/20] sunxi: sync H3, H5, A64 DTs from mainline Linux 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=fe7ffa8a-e8cd-d02c-17f9-28a957b59784@arm.com \
    --to=andre.przywara@arm.com \
    --cc=u-boot@lists.denx.de \
    /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