Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 14 Dec 2020 15:14:00 +0100
From:   Maxime Ripard <maxime@cerno.tech>
To:     Chen-Yu Tsai <wens@csie.org>
Cc:     =?utf-8?B?QW5kcsOp?= Przywara <andre.przywara@arm.com>,
        Jernej Skrabec <jernej.skrabec@siol.net>,
        Icenowy Zheng <icenowy@aosc.xyz>,
        Linus Walleij <linus.walleij@linaro.org>,
        Rob Herring <robh@kernel.org>,
        =?utf-8?B?Q2zDqW1lbnQgUMOpcm9u?= <peron.clem@gmail.com>,
        Shuosheng Huang <huangshuosheng@allwinnertech.com>,
        Yangtao Li <tiny.windzz@gmail.com>,
        linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        linux-sunxi <linux-sunxi@googlegroups.com>,
        devicetree <devicetree@vger.kernel.org>
Subject: Re: [linux-sunxi] Re: [PATCH v2 19/21] arm64: dts: allwinner: Add
 Allwinner H616 .dtsi file
Message-ID: <20201214141400.des3jwfhmbnxd7xe@gilmour>
References: <20201211011934.6171-1-andre.przywara@arm.com>
 <20201211011934.6171-20-andre.przywara@arm.com>
 <20201214095831.j63nks3fqxlaw75w@gilmour>
 <20201214125343.0cd1bc6a@slackpad.fritz.box>
 <CAGb2v677X7h_Xo3L6gP0Ws4P0ROmZ0LhwNStZk-zcL7XtTRCLA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="64zcwd4wdxdwsyj3"
Content-Disposition: inline
In-Reply-To: <CAGb2v677X7h_Xo3L6gP0Ws4P0ROmZ0LhwNStZk-zcL7XtTRCLA@mail.gmail.com>
Precedence: bulk


--64zcwd4wdxdwsyj3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 14, 2020 at 09:28:36PM +0800, Chen-Yu Tsai wrote:
> On Mon, Dec 14, 2020 at 8:53 PM Andre Przywara <andre.przywara@arm.com> w=
rote:
> >
> > On Mon, 14 Dec 2020 10:58:31 +0100
> > Maxime Ripard <maxime@cerno.tech> wrote:
> >
> > Hi,
> >
> > > On Fri, Dec 11, 2020 at 01:19:32AM +0000, Andre Przywara wrote:
> > > > +   reserved-memory {
> > > > +           #address-cells =3D <2>;
> > > > +           #size-cells =3D <2>;
> > > > +           ranges;
> > > > +
> > > > +           /* 512KiB reserved for ARM Trusted Firmware (BL31)
> > > > */
> > > > +           secmon_reserved: secmon@40000000 {
> > > > +                   reg =3D <0x0 0x40000000 0x0 0x80000>;
> > > > +                   no-map;
> > > > +           };
> > > > +   };
> > >
> > > This should still be set by the firmware
> > >
> > > > +           mmc0: mmc@4020000 {
> > > > +                   compatible =3D "allwinner,sun50i-h616-mmc",
> > > > +                                "allwinner,sun50i-a100-mmc";
> > > > +                   reg =3D <0x04020000 0x1000>;
> > > > +                   clocks =3D <&ccu CLK_BUS_MMC0>, <&ccu
> > > > CLK_MMC0>;
> > > > +                   clock-names =3D "ahb", "mmc";
> > > > +                   resets =3D <&ccu RST_BUS_MMC0>;
> > > > +                   reset-names =3D "ahb";
> > > > +                   interrupts =3D <GIC_SPI 35
> > > > IRQ_TYPE_LEVEL_HIGH>;
> > > > +                   pinctrl-names =3D "default";
> > > > +                   pinctrl-0 =3D <&mmc0_pins>;
> > > > +                   status =3D "disabled";
> > > > +                   #address-cells =3D <1>;
> > > > +                   #size-cells =3D <0>;
> > > > +           };
> > >
> > > Somewhat related: we shouldn't set the MMC speed flags in the drivers.
> > > This is biting us on the already supported SoCs, so it would be great
> > > to not repeat the same mistake with the new ones
> >
> > Do you mean to list the "sd-uhs-sdr50" and friends properties here in
> > the DT?
> > What is the best practice here in terms putting them in the .dts vs.
> > the .dtsi? Surely the controller has limits, but bad traces on a board
> > could impose further restrictions, right?
> > Though that's probably rare, so it sounds like a lot of churn to list
> > them in every board DT. So can we list everything in here (.dtsi), then
> > delete in those affected boards only?
>=20
> The driver will most certainly already have the basic high speed modes
> enabled. Or we can list them in the .dtsi file.

I'd list them all in the DTSI, trying to be smart has bitten us already
so I'd like to avoid it as much as possible.

And if we find a better way, we can set it in the driver if it's in the
DTSI already. doing the opposite would be harder

Maxime

--64zcwd4wdxdwsyj3
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCX9dzKAAKCRDj7w1vZxhR
xYxQAQD05F90JhDUdr3GvaKEJQquCi8Tn5R6I8mNQHN9twlqtAEA/M9pX42neqt3
LRIEV6YkIcUb/12pIeA4eDNUBy27sgk=
=gQPC
-----END PGP SIGNATURE-----

--64zcwd4wdxdwsyj3--