From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Date: Tue, 30 Apr 2013 07:28:35 +0000 Subject: Re: [PATCH V2] video: implement a simple framebuffer driver Message-Id: <517F72A3.6010009@ti.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="----enig2UHKKHCHSTVEIUVTHVASA" List-Id: References: <1365043183-28905-1-git-send-email-swarren@wwwdotorg.org> <20130408171637.98b5ad1f867bcbda883af68b@linux-foundation.org> <2569832.XQDrhUGNaI@avalon> <2863648.BDvrAG5uPk@flatron> In-Reply-To: <2863648.BDvrAG5uPk@flatron> To: linux-arm-kernel@lists.infradead.org ------enig2UHKKHCHSTVEIUVTHVASA Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 04/30/2013 12:15 AM, Tomasz Figa wrote: > Well, there is also at least one legitimate use case for this driver. >=20 > I believe there exist embedded devices on which there is no need to=20 > dynamically control the framebuffer. It needs one time initialization, = > usually in bootloader, and then it is used as is, using constant=20 > parameters as long as the system is running. >=20 > I doubt there is a need for any KMS (or any other control) driver for s= uch=20 > devices - dumb framebuffer driver would be everything needed in such ca= se. Isn't there usually the need to power off the hardware when blanking/suspending? Tomi ------enig2UHKKHCHSTVEIUVTHVASA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRf3KjAAoJEPo9qoy8lh71W4AP+wfd4jG+Gmk3CFBu+XdV9xpV hmmbNpN+PLeKVU/+tPZYq/eswVlnwvuEOuOpftstcGqlURP9MUxRKyrnKGvWJjQ+ zoAvM7oIOHzQmKNW39OJQbJdmCXb0si44lJXSvD/4qa311E107eHCOKGTgG0DU5v r7pVkTaiZ7aft8ZReGyFWvE5W4LV2OXVroXVSM5kdfjDOvPT7VBk72cpb0PI3zH7 FA05XmEzNSDcOBrzTfIpwY/2zuQ2fd6KXU6NX64wSkEjasBLIAuooW/8wrqmDM+O p/wuL8uFf8M/hgV9H8JOpyLyMHc0n8j8vLyupO2cpSm23mdtqT0F8zjVAKx1MOsG 3RKp6rXwI7Yapfe79tPny9n9n1N6t4hkp6aLWowpLxOSDcEQHmIgqJKMd93IuchF Hy29nwG5HZlus7AoNeqlGjtDj002Ii14wE5ihJKoodHcxq9lcckrNW/0L6N8OgCa aTSD69HUtoeKIw4yJqrfPyi5qgmg/QhOEM+JGSn6GfDmWPJa9LeyBaUgnb3kWtDn vsb4ZTNUNXl3O4vUJM+xRllP6w3rbjcMDhn4f4wtuxkALrSAy1mNR1G2LorXo3Mb ATku6/uBykIcegF9QhFo4GZ+JzV5EAHeAd0lk98o5nRmEmum/wmVVRCyUOTTwFAa 3MKmm20xNQeKNYLNkI+m =n47N -----END PGP SIGNATURE----- ------enig2UHKKHCHSTVEIUVTHVASA-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: tomi.valkeinen@ti.com (Tomi Valkeinen) Date: Tue, 30 Apr 2013 10:28:35 +0300 Subject: [PATCH V2] video: implement a simple framebuffer driver In-Reply-To: <2863648.BDvrAG5uPk@flatron> References: <1365043183-28905-1-git-send-email-swarren@wwwdotorg.org> <20130408171637.98b5ad1f867bcbda883af68b@linux-foundation.org> <2569832.XQDrhUGNaI@avalon> <2863648.BDvrAG5uPk@flatron> Message-ID: <517F72A3.6010009@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 04/30/2013 12:15 AM, Tomasz Figa wrote: > Well, there is also at least one legitimate use case for this driver. > > I believe there exist embedded devices on which there is no need to > dynamically control the framebuffer. It needs one time initialization, > usually in bootloader, and then it is used as is, using constant > parameters as long as the system is running. > > I doubt there is a need for any KMS (or any other control) driver for such > devices - dumb framebuffer driver would be everything needed in such case. Isn't there usually the need to power off the hardware when blanking/suspending? Tomi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomi Valkeinen Subject: Re: [PATCH V2] video: implement a simple framebuffer driver Date: Tue, 30 Apr 2013 10:28:35 +0300 Message-ID: <517F72A3.6010009@ti.com> References: <1365043183-28905-1-git-send-email-swarren@wwwdotorg.org> <20130408171637.98b5ad1f867bcbda883af68b@linux-foundation.org> <2569832.XQDrhUGNaI@avalon> <2863648.BDvrAG5uPk@flatron> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0156136424708990695==" Return-path: In-Reply-To: <2863648.BDvrAG5uPk@flatron> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Tomasz Figa Cc: linux-fbdev@vger.kernel.org, Arnd Bergmann , Stephen Warren , devicetree-discuss@lists.ozlabs.org, Rob Clark , Laurent Pinchart , Olof Johansson , Andrew Morton , linux-arm-kernel@lists.infradead.org, linux-rpi-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org --===============0156136424708990695== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2UHKKHCHSTVEIUVTHVASA" ------enig2UHKKHCHSTVEIUVTHVASA Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 04/30/2013 12:15 AM, Tomasz Figa wrote: > Well, there is also at least one legitimate use case for this driver. >=20 > I believe there exist embedded devices on which there is no need to=20 > dynamically control the framebuffer. It needs one time initialization, = > usually in bootloader, and then it is used as is, using constant=20 > parameters as long as the system is running. >=20 > I doubt there is a need for any KMS (or any other control) driver for s= uch=20 > devices - dumb framebuffer driver would be everything needed in such ca= se. Isn't there usually the need to power off the hardware when blanking/suspending? Tomi ------enig2UHKKHCHSTVEIUVTHVASA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRf3KjAAoJEPo9qoy8lh71W4AP+wfd4jG+Gmk3CFBu+XdV9xpV hmmbNpN+PLeKVU/+tPZYq/eswVlnwvuEOuOpftstcGqlURP9MUxRKyrnKGvWJjQ+ zoAvM7oIOHzQmKNW39OJQbJdmCXb0si44lJXSvD/4qa311E107eHCOKGTgG0DU5v r7pVkTaiZ7aft8ZReGyFWvE5W4LV2OXVroXVSM5kdfjDOvPT7VBk72cpb0PI3zH7 FA05XmEzNSDcOBrzTfIpwY/2zuQ2fd6KXU6NX64wSkEjasBLIAuooW/8wrqmDM+O p/wuL8uFf8M/hgV9H8JOpyLyMHc0n8j8vLyupO2cpSm23mdtqT0F8zjVAKx1MOsG 3RKp6rXwI7Yapfe79tPny9n9n1N6t4hkp6aLWowpLxOSDcEQHmIgqJKMd93IuchF Hy29nwG5HZlus7AoNeqlGjtDj002Ii14wE5ihJKoodHcxq9lcckrNW/0L6N8OgCa aTSD69HUtoeKIw4yJqrfPyi5qgmg/QhOEM+JGSn6GfDmWPJa9LeyBaUgnb3kWtDn vsb4ZTNUNXl3O4vUJM+xRllP6w3rbjcMDhn4f4wtuxkALrSAy1mNR1G2LorXo3Mb ATku6/uBykIcegF9QhFo4GZ+JzV5EAHeAd0lk98o5nRmEmum/wmVVRCyUOTTwFAa 3MKmm20xNQeKNYLNkI+m =n47N -----END PGP SIGNATURE----- ------enig2UHKKHCHSTVEIUVTHVASA-- --===============0156136424708990695== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============0156136424708990695==--