On 17/06/13 11:40, Igor Grinberg wrote:
> Yes, the reason for this is the sb-t35 (the baseboard) which has the TFP410
> in 3.3V domain, but the cm-t3530/3730 are in 1.8V domain.
> This means that the line must be shifted.
> Now for some reason hardware guys used an inverter as the level shifter
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/17/13 10:08, Tomi Valkeinen wrote:
> On 16/06/13 15:28, Igor Grinberg wrote:
>
Although one thing is missing from the tfp410 driver is
the PD GPIO polarity. I had to adjust it locally to get the DVI working.
The original polarit
On 16/06/13 15:28, Igor Grinberg wrote:
>>> Although one thing is missing from the tfp410 driver is
>>> the PD GPIO polarity. I had to adjust it locally to get the DVI working.
>>> The original polarity was high = disabled, low = enabled.
>
>> Hmm, but this is missing from the old driver also, is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/13/13 19:01, Tomi Valkeinen wrote:
> On 13/06/13 18:51, Igor Grinberg wrote:
>> Hi Tomi,
>>
>> On 06/04/13 10:40, Tomi Valkeinen wrote:
>>> Hi guys,
>>
>>> I've made some big changes on the omapdss device model, which involves
>>> converting al
On 13/06/13 18:51, Igor Grinberg wrote:
> Hi Tomi,
>
> On 06/04/13 10:40, Tomi Valkeinen wrote:
>> Hi guys,
>
>> I've made some big changes on the omapdss device model, which involves
>> converting all the panel drivers. I've got only a bunch of boards, so I
>> hope some of you can perhaps do som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tomi,
On 06/04/13 10:40, Tomi Valkeinen wrote:
> Hi guys,
>
> I've made some big changes on the omapdss device model, which involves
> converting all the panel drivers. I've got only a bunch of boards, so I
> hope some of you can perhaps do some m
On 09/06/13 17:28, Grazvydas Ignotas wrote:
> Hello,
>
> On Tue, Jun 4, 2013 at 10:40 AM, Tomi Valkeinen wrote:
>> I've made some big changes on the omapdss device model, which involves
>> converting all the panel drivers. I've got only a bunch of boards, so I
>> hope some of you can perhaps do s
Hello,
On Tue, Jun 4, 2013 at 10:40 AM, Tomi Valkeinen wrote:
> I've made some big changes on the omapdss device model, which involves
> converting all the panel drivers. I've got only a bunch of boards, so I
> hope some of you can perhaps do some minimal tests on some other boards.
Doesn't work
On 06/06/13 23:43, Aaro Koskinen wrote:
> Hi,
>
> On Tue, Jun 04, 2013 at 10:40:37AM +0300, Tomi Valkeinen wrote:
>> I've made some big changes on the omapdss device model, which involves
>> converting all the panel drivers. I've got only a bunch of boards, so I
>> hope some of you can perhaps do
Hi,
On Tue, Jun 04, 2013 at 10:40:37AM +0300, Tomi Valkeinen wrote:
> I've made some big changes on the omapdss device model, which involves
> converting all the panel drivers. I've got only a bunch of boards, so I
> hope some of you can perhaps do some minimal tests on some other boards.
>
> I'v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tomi,
On 06/04/13 10:40, Tomi Valkeinen wrote:
> Hi guys,
>
> I've made some big changes on the omapdss device model, which involves
> converting all the panel drivers. I've got only a bunch of boards, so I
> hope some of you can perhaps do some m
Hi guys,
I've made some big changes on the omapdss device model, which involves
converting all the panel drivers. I've got only a bunch of boards, so I
hope some of you can perhaps do some minimal tests on some other boards.
I've got: Beagle (old one), Panda, 4430SDP, Overo with LCD43.
The code
12 matches
Mail list logo
