From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: [PATCHv3 04/30] drm/omap: decrease min width & height Date: Wed, 29 Mar 2017 11:43:33 +0300 Message-ID: References: <1490706496-4959-1-git-send-email-tomi.valkeinen@ti.com> <1867154.MpK1o854Pl@avalon> <03c89160-af6e-d6fd-7cf3-7f4ae4179ee6@ti.com> <1523334.5aL05G15qn@avalon> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0234251029==" Return-path: Received: from lelnx194.ext.ti.com (lelnx194.ext.ti.com [198.47.27.80]) by gabe.freedesktop.org (Postfix) with ESMTPS id 1AF0E6E6EB for ; Wed, 29 Mar 2017 08:43:39 +0000 (UTC) In-Reply-To: <1523334.5aL05G15qn@avalon> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Laurent Pinchart Cc: Jyri Sarha , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0234251029== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Re7DtvkrdUfO3o0DPtKdvpcEeRKH0QwPE" --Re7DtvkrdUfO3o0DPtKdvpcEeRKH0QwPE Content-Type: multipart/mixed; boundary="ppqHUQVPWn0plrsexNlb6rSjllk5Q6HVv"; protected-headers="v1" From: Tomi Valkeinen To: Laurent Pinchart Cc: dri-devel@lists.freedesktop.org, Jyri Sarha Message-ID: Subject: Re: [PATCHv3 04/30] drm/omap: decrease min width & height References: <1490706496-4959-1-git-send-email-tomi.valkeinen@ti.com> <1867154.MpK1o854Pl@avalon> <03c89160-af6e-d6fd-7cf3-7f4ae4179ee6@ti.com> <1523334.5aL05G15qn@avalon> In-Reply-To: <1523334.5aL05G15qn@avalon> --ppqHUQVPWn0plrsexNlb6rSjllk5Q6HVv Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 29/03/17 11:30, Laurent Pinchart wrote: > The mode setting min/max width and height are used by the core when cre= ating a=20 > framebuffer to validate its size. It's thus only related to planes, not= to the=20 > CRTC. It's also set to drm_mode_card_res, and fb's min & max are not necessarily the same as plane's min and max. But yes, I think you're right, it's not related to crtc as such. With legacy the fb min defines the crtc min (I think), but possibly with atomic that's not true. It's a bit messed up, really. We should have separate limits for crtcs, planes and fbs. For now the mode_config is all we have. Tomi --ppqHUQVPWn0plrsexNlb6rSjllk5Q6HVv-- --Re7DtvkrdUfO3o0DPtKdvpcEeRKH0QwPE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJY23O2AAoJEPo9qoy8lh71D5MP/RDwXxhGrczhPBQxfNHeJjBB 2klBLlAnva3489aRom5Q6ERXR9N5KiC9zxpI37vOA3Wbw1O9mPMYFcYeDs6YK6Pg sdxSQIUaC2wKbSH35Pq87JyxnGwGuk1dTvNsBNd3RzJzevfHDshEpdaF8Ej+s/Cm r90JnQU1N4Sw+ZI3k1C8ASdHWTJNKL6HBui4Kfk6U67jwqF2i4M7Dw1eIF91YnUS 3k5NTXBF4+5Bsmwg0Y19+XCRoRS2J6IfIjO1YMlYsUulSggse7VOfBS+N8yOIQ7l dRqitW8LoOZoi2B2hj/bCW6ZpLJ0d0n0E/T5x2IgimeXtn+SJ3VvU3VXmnHD16nl mODHkJOvdMrxvZtblgFyVYLlbrbvJSfEjp3Nj9P4jq0J1MOPWQfP0KDnCee8+qaF J/Rnc02+MHHDCwrTOcFh61I/nGrtij08YQPwFMNEltjzjCq640kCuKms35JWv3gR DIPtZ0o2sXeWrJWtHoFksrUTODPNHAIiMi+o95JKSL/v0zrwCDk8O6l+Cm2fsZ04 6277sUkhMR+RWBOmGJRp8BYZzTwHxY0P7U7HF3w8B9NOybMX0sloLsvTvoAh1QD+ L2F09N8HBq8jZ6YEAExVCjP9gbmR12rRSLQn4crt9UHVezVhIWlq00iMomuS5Blh OzlyfTggQAFCuH96ut2a =/9cR -----END PGP SIGNATURE----- --Re7DtvkrdUfO3o0DPtKdvpcEeRKH0QwPE-- --===============0234251029== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0234251029==--