Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
Date:   Mon, 30 Oct 2023 14:39:21 +0100
From:   Maxime Ripard <mripard@kernel.org>
To:     Sui Jingfeng <suijingfeng@loongson.cn>
Cc:     Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
        Thomas Zimmermann <tzimmermann@suse.de>,
        linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/8] drm/loongson: Introduce a drm bridge driver for
 it66121 HDMI transmitter
Message-ID: <e4ozgwe7g5s3bioywxqcetuqwxk6byvz2lr3swlgy7wutxcxkp@obvvszcgz2qw>
References: <20231029194607.379459-1-suijingfeng@loongson.cn>
 <20231029194607.379459-3-suijingfeng@loongson.cn>
 <CAA8EJprjQXcTgxnC1POaBjVBzyVBvKpmKyJcCR5ExRUhVxtYoQ@mail.gmail.com>
 <3ccb9600-6990-4ec7-81de-0d7b4e1294eb@loongson.cn>
 <CAA8EJpqCe2j3GyeutnwTB0bkGXGk0az9-w3sPHLFwMVgAS=e7g@mail.gmail.com>
 <df176548-0001-4df4-b556-6227b776cd18@loongson.cn>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="2cbip6tmp5j2oowq"
Content-Disposition: inline
In-Reply-To: <df176548-0001-4df4-b556-6227b776cd18@loongson.cn>
Precedence: bulk


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

On Mon, Oct 30, 2023 at 09:25:50PM +0800, Sui Jingfeng wrote:
> I think my approach provide a solution, while still keep the bridges driv=
ers
> to a modular at the same time. Despite simple, it indeed solve the proble=
m.
> It simple because of explicit control of the loading order by myself, not=
 by
> rely on the framework or something else (say component)
>=20
> It is not totally duplicating, I have rewrite part of them. You can compa=
re
> to see what I'm changed. It is just that it66162 was upstream-ed earlier =
than
> our solution. But I also have write display drivers for lt8618 and lt8619
> completely by myself.
>
> Even though our local drm bridges driver will not be able to enjoy the up=
dates.
> We will accept such a results(or pain). I can maintain our local drm brid=
ges
> drivers by myself. Sorry, on this technique point, we will not follow you=
r idea.
> I'm sure that my approach is toward to right direction for our device at =
now.
> If someone invent a better solution to handle this problem, which make the
> various drm bridges drivers usable out of box, then I will follow and coo=
perate
> to test.

As far as I'm concerned, the two options are either you reuse the
already existing driver or this series isn't merged.

Ignoring what issue we raised and still merging your patch isn't on the
table, sorry.

Maxime

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

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

iHUEABYKAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCZT+yCQAKCRDj7w1vZxhR
xWvFAP9k53SCPnaxsg9Uc5iHT3bjHKTMhbl+/6pokYTmjiB9WgD9FNBO2ztxI2Ah
lg/MJmIFuKoV4egJ7R5B5n987tYHZQk=
=hZBP
-----END PGP SIGNATURE-----

--2cbip6tmp5j2oowq--