All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alex Courbot <acourbot@nvidia.com>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Olof Johansson <olof@lixom.net>,
	"gnurou@gmail.org" <gnurou@gmail.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH] simplefb: add support for a8b8g8r8 pixel format
Date: Thu, 06 Jun 2013 16:11:14 +0000	[thread overview]
Message-ID: <51B0B4A2.4010104@wwwdotorg.org> (raw)
In-Reply-To: <51B0446A.4090305@nvidia.com>

On 06/06/2013 02:12 AM, Alex Courbot wrote:
> On 06/06/2013 04:59 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>
>> On Jun 6, 2013, at 9:20 AM, Alexandre Courbot <acourbot@nvidia.com>
>> wrote:
>>
>>> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>

No commit description? It'd be useful to at least justify this by
mentioning that some platform will actually use this...

...
>>> static struct simplefb_format simplefb_formats[] = {
>>>     { "r5g6b5", 16, {11, 5}, {5, 6}, {0, 5}, {0, 0} },
>>> +    { "a8b8g8r8", 32, {0, 8}, {8, 8}, {16, 8}, {31, 8} },
>>
>> why don't you parse the string?
>>
>> so you will a real generic bindings
> 
> Tried that already, got NACKed: https://lkml.org/lkml/2013/5/27/330
> 
> The list of modes of this driver should not grow too big. Even in terms
> of footprint I'd say the list should remain smaller than the parsing code.
> 
> What we can discuss though is whether we want to keep this a8b8g8r8
> syntax or switch to something more standard, say "rgba8888".

I would prefer to keep the syntax of the new formats consistent, so that
if we ever do add format-parsing code rather than table-based lookup,
all the existing formats will continue to work unchanged, without any
kind of fallback lookup table.

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alex Courbot <acourbot@nvidia.com>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Olof Johansson <olof@lixom.net>,
	"gnurou@gmail.org" <gnurou@gmail.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH] simplefb: add support for a8b8g8r8 pixel format
Date: Thu, 06 Jun 2013 10:11:14 -0600	[thread overview]
Message-ID: <51B0B4A2.4010104@wwwdotorg.org> (raw)
In-Reply-To: <51B0446A.4090305@nvidia.com>

On 06/06/2013 02:12 AM, Alex Courbot wrote:
> On 06/06/2013 04:59 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>
>> On Jun 6, 2013, at 9:20 AM, Alexandre Courbot <acourbot@nvidia.com>
>> wrote:
>>
>>> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>

No commit description? It'd be useful to at least justify this by
mentioning that some platform will actually use this...

...
>>> static struct simplefb_format simplefb_formats[] = {
>>>     { "r5g6b5", 16, {11, 5}, {5, 6}, {0, 5}, {0, 0} },
>>> +    { "a8b8g8r8", 32, {0, 8}, {8, 8}, {16, 8}, {31, 8} },
>>
>> why don't you parse the string?
>>
>> so you will a real generic bindings
> 
> Tried that already, got NACKed: https://lkml.org/lkml/2013/5/27/330
> 
> The list of modes of this driver should not grow too big. Even in terms
> of footprint I'd say the list should remain smaller than the parsing code.
> 
> What we can discuss though is whether we want to keep this a8b8g8r8
> syntax or switch to something more standard, say "rgba8888".

I would prefer to keep the syntax of the new formats consistent, so that
if we ever do add format-parsing code rather than table-based lookup,
all the existing formats will continue to work unchanged, without any
kind of fallback lookup table.

  parent reply	other threads:[~2013-06-06 16:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  7:20 [PATCH] simplefb: add support for a8b8g8r8 pixel format Alexandre Courbot
2013-06-06  7:20 ` Alexandre Courbot
2013-06-06  7:59 ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06  7:59   ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06  8:12   ` Alex Courbot
2013-06-06  8:12     ` Alex Courbot
2013-06-06  8:24     ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06  8:24       ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06  8:27       ` Alex Courbot
2013-06-06  8:27         ` Alex Courbot
2013-06-06 14:50         ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06 14:50           ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06 16:17           ` Stephen Warren
2013-06-06 16:17             ` Stephen Warren
2013-06-06 16:29             ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06 16:29               ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06 16:45               ` Stephen Warren
2013-06-06 16:45                 ` Stephen Warren
2013-06-06 16:11     ` Stephen Warren [this message]
2013-06-06 16:11       ` Stephen Warren
2013-06-06 16:20       ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06 16:20         ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06 16:33         ` Olof Johansson
2013-06-06 16:33           ` Olof Johansson
2013-06-06 16:32           ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-06 16:32             ` Jean-Christophe PLAGNIOL-VILLARD
2013-06-07  6:08             ` Alex Courbot
2013-06-07  6:08               ` Alex Courbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51B0B4A2.4010104@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=acourbot@nvidia.com \
    --cc=gnurou@gmail.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=plagnioj@jcrosoft.com \
    --cc=tomi.valkeinen@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.