From: Petr Cvek <petr.cvek@tul.cz>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1, TRIVIAL] Fix pxafb nonstd field documentation and add errata info
Date: Thu, 20 Aug 2015 20:07:45 +0000 [thread overview]
Message-ID: <55D63391.3080403@tul.cz> (raw)
In-Reply-To: <55D5B232.9090006@ti.com>
Dne 20.8.2015 v 12:55 Tomi Valkeinen napsal(a):
>
>
> On 08/08/15 21:20, Petr Cvek wrote:
>
>> diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
>> index 2d98de5..8f485ec 100644
>> --- a/drivers/video/fbdev/Kconfig
>> +++ b/drivers/video/fbdev/Kconfig
>> @@ -1893,6 +1893,11 @@ config FB_PXA_OVERLAY
>> bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
>> default n
>> depends on FB_PXA && (PXA27x || PXA3xx)
>> + ---help---
>> + Using the overlay 2 and YUV420 mode on a PXA27x C0 chip revision will
>> + hang the LCD until the next SoC restart (errata E24).
>
> Shouldn't the driver handle this? It should not allow the combination to
> be used.
>
> Tomi
>
Probably, but I don't know which revisions are OK and which are not. Errata document:
Marvell® PXA270M Processor Specification Update
MV-S900957-00
has only 3 revisions, but PXA Manual lists 6 (2.2.5.1 Processor ID Register) and one revision from errata is not shown in my PXA Manual. I can exclude mine revision (from "system_rev" variable), but there should be some warning somewhere in configuration.
BTW There is software workaround, but I was not able to set registers right (it requires to send some data through FIFO in different mode).
Petr
WARNING: multiple messages have this Message-ID (diff)
From: petr.cvek@tul.cz (Petr Cvek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1, TRIVIAL] Fix pxafb nonstd field documentation and add errata info
Date: Thu, 20 Aug 2015 22:07:45 +0200 [thread overview]
Message-ID: <55D63391.3080403@tul.cz> (raw)
In-Reply-To: <55D5B232.9090006@ti.com>
Dne 20.8.2015 v 12:55 Tomi Valkeinen napsal(a):
>
>
> On 08/08/15 21:20, Petr Cvek wrote:
>
>> diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
>> index 2d98de5..8f485ec 100644
>> --- a/drivers/video/fbdev/Kconfig
>> +++ b/drivers/video/fbdev/Kconfig
>> @@ -1893,6 +1893,11 @@ config FB_PXA_OVERLAY
>> bool "Support PXA27x/PXA3xx Overlay(s) as framebuffer"
>> default n
>> depends on FB_PXA && (PXA27x || PXA3xx)
>> + ---help---
>> + Using the overlay 2 and YUV420 mode on a PXA27x C0 chip revision will
>> + hang the LCD until the next SoC restart (errata E24).
>
> Shouldn't the driver handle this? It should not allow the combination to
> be used.
>
> Tomi
>
Probably, but I don't know which revisions are OK and which are not. Errata document:
Marvell? PXA270M Processor Specification Update
MV-S900957-00
has only 3 revisions, but PXA Manual lists 6 (2.2.5.1 Processor ID Register) and one revision from errata is not shown in my PXA Manual. I can exclude mine revision (from "system_rev" variable), but there should be some warning somewhere in configuration.
BTW There is software workaround, but I was not able to set registers right (it requires to send some data through FIFO in different mode).
Petr
next prev parent reply other threads:[~2015-08-20 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 18:20 [PATCH v1, TRIVIAL] Fix pxafb nonstd field documentation and add errata info Petr Cvek
2015-08-08 18:20 ` Petr Cvek
2015-08-08 19:15 ` Robert Jarzmik
2015-08-08 19:15 ` Robert Jarzmik
2015-08-20 10:55 ` Tomi Valkeinen
2015-08-20 10:55 ` Tomi Valkeinen
2015-08-20 20:07 ` Petr Cvek [this message]
2015-08-20 20:07 ` Petr Cvek
2015-08-21 6:53 ` Tomi Valkeinen
2015-08-21 6:53 ` Tomi Valkeinen
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=55D63391.3080403@tul.cz \
--to=petr.cvek@tul.cz \
--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 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.