From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Anholt Subject: Re: [GIT PULL] MT8173 DRM support Date: Wed, 20 Apr 2016 09:21:17 -0700 Message-ID: <87potks136.fsf@eliezer.anholt.net> References: <1461073370.3542.22.camel@pengutronix.de> <571785D0.6060803@gmail.com> <20160420151957.GN2510@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0034966222==" Return-path: Received: from anholt.net (anholt.net [50.246.234.109]) by gabe.freedesktop.org (Postfix) with ESMTP id 89D436E8E2 for ; Wed, 20 Apr 2016 16:21:26 +0000 (UTC) In-Reply-To: <20160420151957.GN2510@phenom.ffwll.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Daniel Vetter , Matthias Brugger Cc: kernel@pengutronix.de, dri-devel@lists.freedesktop.org, Cawa Cheng , Jie Qiu List-Id: dri-devel@lists.freedesktop.org --===============0034966222== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Daniel Vetter writes: > On Wed, Apr 20, 2016 at 03:36:16PM +0200, Matthias Brugger wrote: >>=20 >>=20 >> On 19/04/16 15:42, Philipp Zabel wrote: >> >Hi Dave, >> > >> >please consider pulling this tag with initial MediaTek MT8173 DRM >> >support, corresponding to v14 of the patch series. These patches have >> >been mostly stable for the last few rounds. I'll follow up with the HDMI >> >encoder support pending review of the latest version. >> > >>=20 >> Please don't pull >> e34ba70de8c4 ("arm64: dts: mt8173: Add display subsystem related nodes") >> If you pull the rest, this patch will go through my branch. > > So not on top of this at all, but do we have to split up arm drm drivers > so much? Generally this stuff goes in through one tree with the driver, > with acks from other subsystem as needed. That ack seems to be missing, > but imo better to supply it and just get this pull req through. Or double > merge a patch, we do that fairly often. > > Anyway just a comment, but sitting outside watching I think arm has a > pretty serious problem with tree proliferation. And it's not helping to > get fairly simple drivers like this one merged ... DT changes do get merged through the arm DT tree separately. ARM has absurd tree proliferation, but I think in this case it actually makes sense. DT is the most common place I have merge conflicts when working on platform enabling across the steaming piles of subsystem trees out there, and keeping DT separate means that a merged -next tree can be built sanely. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJXF6x9AAoJELXWKTbR/J7ovSoQALRqUi6Md5BAAAYjLXRuK6c4 F/LefEmzOjFz6XtNSBbVwWkJrMxe3WBJaCZuxASBV67f80DZEge9boq91URy39vK lV6SW43rMZ53M+E9YIHFn/kaE4yiwuB4XP96u3PBhPl6qa2tDjgt28P7DBXd9NMP VqCXhFSegAyNEDN/6YvLY47VVMCEk5flR6mC5uGLYwGOBibOfWG5d50mZMC8qeP/ gkTVCui8k4zRSmOfrn2vMH3zPofT6rBO5h31p1amJZs75GXy1U8cLrVqwtGJEmDy m16Us8+6YL/kaZQ+UPG6EjhNTBSkPlzXYajcdZ1gofNUo9K6JHTSjiwQ6rlZx6qz imYSR0JE14C/NvzDjm/f9NPQO0pK+fCxJcV9Ya0qtfbe8LtG8uuWu+O0xRxesNrL WNyUaoy8QBnFCtxPVm+4SOXuCXJrC/QPZGtMikXvZWrCmMAwG33MZS4fyzAu0yhp TyD7gbFJ/r30oCv1+yclWIGSpjLVgHA7TlcKkQO0/9kRgMueW4ErwO1KIqTZXirw yjGeEcn/DWqcV9duHGzFHevBGjLJR+NafDQFTkyJpxGVawzjMsAN+LIfCQ4IQ+4j f2bWqLpzsfj9GrngnZbzSffrhhOsZxIyfQKdOiyGGosyEDHSgzZP55ytsDNNGeCS U/oCcF0wC4Hz/lu9f8n6 =qPG+ -----END PGP SIGNATURE----- --=-=-=-- --===============0034966222== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0034966222==--