[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BY5PR02MB70094BBCBE78A146A8C4CA0AD9D69@BY5PR02MB7009.namprd02.prod.outlook.com>
Date: Wed, 25 May 2022 18:33:52 +0530
From: Joel Selvaraj <jo@...amily.in>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: devicetree@...r.kernel.org, Hao Fang <fanghao11@...wei.com>,
David Airlie <airlied@...ux.ie>,
Sam Ravnborg <sam@...nborg.org>,
~postmarketos/upstreaming@...ts.sr.ht,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
Oleksij Rempel <linux@...pel-privat.de>,
Rob Herring <robh+dt@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
phone-devel@...r.kernel.org, Shawn Guo <shawnguo@...nel.org>,
Stanislav Jakubek <stano.jakubek@...il.com>,
Corentin Labbe <clabbe@...libre.com>
Subject: Re: [PATCH 3/3] drm/panel: introduce ebbg,ft8719 panel
Hi Linus Walleij
On 19/05/22 14:39, Linus Walleij wrote:
> Nope. But add the rate limited error print please!
Will do.
>>> Lots of magic numbers. You don't have a datasheet do you?
>>> So you could #define some of the magic?
>>
>> Unfortunately, I don't have a datasheet and the power on sequence is
>> taken from downstream android dts. It works pretty well though. So I
>> don't think I can #define any of these magic.
>
> If you know which display controller the display is using (usually
> Novatek nnnnn, Ilitek nnnn etc someting like that) there is often
> a datasheet for the display controller available but the display per
> se often obscures the display controller.
Well, I recently figured that the panel works perfectly without all the
magic commands. So, no need for #defines of those magics/documentation
for now.
>> > Doesn't it work to combine them into one call for each
>> > pair?
>> >> + dsi_dcs_write_seq(dsi, );
>> >> + dsi_generic_write_seq(dsi, 0xff, 0x87, 0x19);
>>
>> By using a macro? We can... but I am not sure what (0x00, 0x80), (0x00,
>> 0xa0),etc type of commands signify without the datasheet, so I am not
>> sure what to name them in the macro and make any sensible meaning out of it.
>
> I meant just sending dsi_generic_write_seq() with everything in
> it:
>
> dsi_generic_write_seq(dsi, 0x00, 0x80, 0xff, 0x87, 0x19);
>
> Instead of two writes. Doesn't this work?
I am not sure about whether it will work. Can multiple DCS commands can
be combined into single write? Don't know much about this.
Anyways since the panel works without all these magic commands, these
will be removed in the next version.
> Yours,
> Linus Walleij
Thanks and Regards
Joel Selvaraj
Powered by blists - more mailing lists