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:   Tue, 1 Dec 2020 11:35:19 +0100
From:   Maxime Ripard <maxime@cerno.tech>
To:     =?utf-8?B?Q2zDqW1lbnQgUMOpcm9u?= <peron.clem@gmail.com>
Cc:     Icenowy Zheng <icenowy@aosc.io>,
        Samuel Holland <samuel@sholland.org>,
        devicetree <devicetree@vger.kernel.org>,
        Jernej Skrabec <jernej.skrabec@siol.net>,
        linux-sunxi <linux-sunxi@googlegroups.com>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
        linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [linux-sunxi] Re: [PATCH 3/3] arm64: allwinner: dts: a64: add DT
 for PineTab developer sample
Message-ID: <20201201103519.b7rbkmjssmvy6qeo@gilmour>
References: <38ee5feb-e35d-801f-99a1-65e23618e73b@sholland.org>
 <20201123111512.y7lbwsipbkcpuleb@gilmour>
 <97E2037C-3C3C-4B0B-8462-39B9E38CB3BB@aosc.io>
 <20201123125332.2p5z3ew7svszvyfs@gilmour>
 <009A22D9-AF20-45C4-9674-13334B3EFFBA@aosc.io>
 <20201128103827.d6sfc2eumli2betx@gilmour>
 <1666a61f6ea3e7d573795f9000a0b096c7b7dee0.camel@aosc.io>
 <CAJiuCcfEcM+Dksm4uoRPCiRepDSnEmp7pr8Qk5EsFSH_zEOTYA@mail.gmail.com>
 <C8F86F90-14BF-4857-9DB8-7968A34E4656@aosc.io>
 <CAJiuCcc=s6xG7Wzfx6PBU0e3BHz+YRpU=t0Ef3EcTp9k11Dkzg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="rgqpgfhy623krart"
Content-Disposition: inline
In-Reply-To: <CAJiuCcc=s6xG7Wzfx6PBU0e3BHz+YRpU=t0Ef3EcTp9k11Dkzg@mail.gmail.com>
Precedence: bulk


--rgqpgfhy623krart
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Nov 28, 2020 at 10:07:27PM +0100, Cl=C3=A9ment P=C3=A9ron wrote:
> Hi Maxime, Icenowy,
>=20
> On Sat, 28 Nov 2020 at 12:59, Icenowy Zheng <icenowy@aosc.io> wrote:
> >
> >
> >
> > =E4=BA=8E 2020=E5=B9=B411=E6=9C=8828=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=8D=
=887:54:04, "Cl=C3=A9ment P=C3=A9ron" <peron.clem@gmail.com> =E5=86=99=E5=
=88=B0:
> > >Hi Icenowy,
> > >
> > >On Sat, 28 Nov 2020 at 12:28, Icenowy Zheng <icenowy@aosc.io> wrote:
> > >>
> > >> =E5=9C=A8 2020-11-28=E6=98=9F=E6=9C=9F=E5=85=AD=E7=9A=84 11:38 +0100=
=EF=BC=8CMaxime Ripard=E5=86=99=E9=81=93=EF=BC=9A
> > >> > On Mon, Nov 23, 2020 at 09:10:38PM +0800, Icenowy Zheng wrote:
> > >> > > > > > > > Okay. But I'm not satisfied with a non-public sample
> > >> > > > > > > > occupies
> > >> > > > > > > > the pinetab name. Is rename it to pinetab-dev and add a
> > >> > > > > > > > pinetab-retail okay?
> > >> > > > > > >
> > >> > > > > > > To me, naming the production version anything but
> > >"pinetab"
> > >> > > > > > > isn't
> > >> > > > > > > satisfying either.
> > >> > > > > >
> > >> > > > > > I understand where you're coming from, but the point I was
> > >> > > > > > making my
> > >> > > > > > previous mail is precisely that it's not really possible.
> > >> > > > > >
> > >> > > > > > You want to name the early adopter version _the_ production
> > >> > > > > > version. Let's assume the hardware changes again between
> > >the
> > >> > > > > > early
> > >> > > > > > adopter and mass-production version. Which one will be
> > >_the_
> > >> > > > > > production version? The early-adopter or the mass-produced
> > >> > > > > > one?
> > >> > > > > >
> > >> > > > > > There's really no good answer here, and both would suck in
> > >> > > > > > their
> > >> > > > > > own way. The only way to deal with this is to simply avoid
> > >> > > > > > defining one version as the one true board, and just
> > >loading
> > >> > > > > > the
> > >> > > > > > proper DT in u-boot based on whatever clue we have of the
> > >> > > > > > hardware
> > >> > > > > > revision.
> > >> > > > > Then will it be okay to rename current pinetab DT to
> > >> > > > > pinetab-sample and then introduce new DTs all with suffixes?
> > >> > > >
> > >> > > > No. From my previous mail:
> > >> > >
> > >> > > It can be seen as dropping the PineTab DT and introduce new DTs
> > >> > > with
> > >> > > suffix.
> > >> > >
> > >> > > Do we have rule that we cannot drop boards?
> > >> >
> > >> > Are you really arguing that removing a DT and then adding an
> > >> > identical
> > >> > one under a different name is not renaming it?
> > >>
> > >> Then we can just keep confusing name?
> > >
> > >Sorry maybe I missed some information
> > >But why don't you do like pinephone?
> >
> > They're the same board revision with different LCD panels.
>=20
> I just ask Pine64 about this and here is the reply :
> "The PineTab LCD panel change was a last minutes before production
> starts that vendor advise us switch over to new LCD controller due to
> EoL concern".
>=20
> "Pine64 communication" is not so bad we just need to ask and they reply :)
>=20
> So the issue is not that the Product was not finalized but that one
> component arrives in EoL.
> This could also happens during a running production.

Like you said, it can happen pretty much any time, for any reason, so
the intent doesn't really matter here.

Maxime

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

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

iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCX8YcZwAKCRDj7w1vZxhR
xYH3AP0dPxkYv/U6VJA+t3uPWhK00GwYTZ3CFhfHVGf/HccA6gD/dKv7K797LKRy
FdumRXFytt561Lnmzp/j2JD29QjL9AY=
=eIGA
-----END PGP SIGNATURE-----

--rgqpgfhy623krart--