linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] at91: atmel_lcdfb: regression fixes and cpu_is removal
Date: Fri, 08 Mar 2013 09:37:45 +0000	[thread overview]
Message-ID: <5139B169.7050807@atmel.com> (raw)
In-Reply-To: <CAMgPeKV4=C_msvZixVS-o3-QHaJxZP7T4EwLa9vnmYgVheXHgQ@mail.gmail.com>

On 02/10/2013 07:45 PM, Johan Hovold :
> On Sun, Feb 10, 2013 at 1:47 AM, Olof Johansson <olof@lixom.net> wrote:
>> On Fri, Feb 08, 2013 at 05:35:13PM +0100, Nicolas Ferre wrote:
>>> These patches fix a regression in 16-bpp support for older SOCs which
>>> use IBGR:555 rather than BGR:565 pixel layout. Use SOC-type to
>>> determine if the controller uses the intensity-bit and restore the
>>> old layout in that case.
>>>
>>> The last patch is a removal of uses of cpu_is_xxxx() macros in
>>> atmel_lcdfb with a platform-device-id table and static
>>> configurations.
>>>
>>>
>>> Patches from Johan Hovold taken from: "[PATCH 0/3] atmel_lcdfb: fix
>>> 16-bpp regression" and "[PATCH v2 0/3] ARM: at91/avr32/atmel_lcdfb:
>>> remove cpu_is macros" patch series to form a clean patch series with
>>> my signature.
>>>
>>> Arnd, Olof, as it seems that old fbdev drivers are not so much
>>> reviewed those days, can we take the decision to queue this material
>>> through arm-soc with other AT91 drivers updates?
>>
>> It would be beneficial to get an ack from Florian. Was he involved in
>> the review of the code that regressed 16-bpp support in the first
>> place? When was the regression introduced?
> 
> In v3.4 by commit 787f9fd2328 ("atmel_lcdfb: support 16bit BGR:565 mode,
> remove unsupported 15bit modes").

Arnd, Olof,

Please tell me if I can do something to ease the adoption of these
patches during 3.9-rc timeframe (I can rebase it on top of 3.9-rc1 to
avoid any conflict: the file board-neocore926.c was removed during the
merge window).
Johan has written the series a long time ago and we still do not have it
in mainline.

If the option to ask Andrew is better in your opinion, please tell me.

Best regards,
-- 
Nicolas Ferre

  reply	other threads:[~2013-03-08  9:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 16:35 [PATCH 0/5] at91: atmel_lcdfb: regression fixes and cpu_is removal Nicolas Ferre
2013-02-08 16:35 ` [PATCH 1/5] atmel_lcdfb: fix 16-bpp modes on older SOCs Nicolas Ferre
2013-02-08 16:35 ` [PATCH 2/5] ARM: at91/neocore926: fix LCD-wiring mode Nicolas Ferre
2013-02-08 16:35 ` [PATCH 3/5] ARM: at91/avr32/atmel_lcdfb: add bus-clock entry Nicolas Ferre
2013-02-08 16:35 ` [PATCH 4/5] atmel_lcdfb: move lcdcon2 register access to compute_hozval Nicolas Ferre
2013-02-08 16:35 ` [PATCH 5/5] ARM: at91/avr32/atmel_lcdfb: add platform device-id table Nicolas Ferre
2013-02-08 16:52 ` [PATCH 0/5] at91: atmel_lcdfb: regression fixes and cpu_is removal Jean-Christophe PLAGNIOL-VILLARD
2013-02-10  0:47 ` Olof Johansson
2013-02-10 18:45   ` Johan Hovold
2013-03-08  9:37     ` Nicolas Ferre [this message]
2013-03-13 10:12       ` Nicolas Ferre
2013-03-14 23:03         ` Arnd Bergmann
2013-03-15 10:16           ` Nicolas Ferre
2013-03-04 14:51   ` Johan Hovold

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=5139B169.7050807@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).